Independent Versioning and Release Process
Consumed API from other projects
| Project | API Dependency | Notes | |||
|---|---|---|---|---|---|
| Portal | 2.1.0 | When portal team releases we will upgrade. | Dmaap | Linking directly to github Open Source version from R0 | Unable to upgrade to re-packaged client libraries in ONAP due to time considerations via blocker B24|
| AAF | v2.1.0 | ||||
| Dmaap | v1.1.3 | ||||
| AAI | v11 | No direct link to any libraries | |||
| APP-C | No direct link to any libraries | ||||
| SO | No direct link to any libraries | ||||
| VFC | No direct link to any libraries |
Published API - These projects use the policy libraries to build their code
| Project | API | Notes |
|---|---|---|
| CLAMP | 1.2.0 | |
| DCAE | n/a | Implemented own python API |
1. Follow the process as outlined here: Independent Versioning and Release Process. Policy repositories inherit from oparent so release jobs will fail if any SNAPSHOT artifact is referenced in the pom.xml's.
- Verify there are no SNAPSHOTs and we are up-to-date with other team's released artifacts.
- Send Helpdesk tickets to LF ONAP release engineering specifying the Jenkin's Job to release Java artifacts and then the docker images
- Update the Integration team manifest so public knows what released artifacts are available. Example gerrit review: https://gerrit.onap.org/r/#/c/42709/
- Update the Demo team heat scripts so the automated External Lab Jobs work and the Integration team has the latest artifacts for testing.
- Example gerrit review: https://gerrit.onap.org/r/#/c/42711/
- If the branch has occurred, then we must also ensure the heat points to the correct branch: https://gerrit.onap.org/r/#/c/49869/1
- Update the OOM team K8S Helm Charts. Example gerrit review: https://gerrit.onap.org/r/#/c/42713/
2. For any new changes to be done post-Release. Then the we must update to the next SNAPSHOT version:
| Repo | Notes | Example Commit(s) | |
|---|---|---|---|
| policy/common | all pom.xml's version.properties | https://gerrit.onap.org/r/#/c/2810742781/ | |
| policy/drools- | applicationspdp | all pom.xml's version.properties | |
| policy/drools- | pdpapplications | all pom.xml's version.properties | |
| policy/engine | all pom.xml's version.properties BRMSGateway/config.properties BRMSGateway/dependency.json BRMSGateway/src/main/java/org/onap/policy/brms/brmsInterfaceapi/BRMSPush.java BRMSGateway/src/test/resources/config.properties | https://gerrit.onap.org/r/#/c/2811342809/ | |
| policy/docker | all pom.xml's version.propertiesThere are no artifacts in this repo. But we need to be sure that any scripts that pull anything like templates are updated when branching. config/pe/brmsgwpush-policies.confsh | https://gerrit.onap.org/r/#/c/ 28185 |
When branching, its easiest to update the .gitreview file ON the new branch in order to ensure that new gerritt submissions are tracked on that branch.
...