Consumed API from other projects
...
| Release Order | Repo (released version) | Notes | Example Commit(s) for upgrading versions |
|---|---|---|---|
| 1 | policy/parent 3.1.3 | all pom.xml's version.properties | https://gerrit.onap.org/r/c/policy/parent/+/104021 |
| 2a | policy/docker 2.0.1 | all pom.xml's version.properties | https://gerrit.onap.org/r/c/policy/docker/+/102678 |
| 2b | policy/common 1.6.5 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/common/+/104047 |
| 3 | policy/models 2.2.6 | all pom.xml's version.properties In main pom.xml change the following properties
BRMS_MODELS_DEPENDENCY_VERSION
| |
| 4a | policy/api 2.2.4 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/api/+/104257 |
| 4b | policy/pap 2.2.3 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/pap/+/104262 |
| 4c | policy/drools-pdp 1.6.3 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
Update policy/drools-applications files:
| |
| 4d | policy/apex-pdp 2.3.2 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
| |
| 4e | policy/xacml-pdp 2.2.2 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
| https://gerrit.onap.org/r/c/policy/xacml-pdp/+/104294 |
| 4f | policy/distribution 2.3.2 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/distribution/+/104296 |
| 5 - Dependent only on policy/drools-pdp | policy/drools-applications 1.6.4 | all pom.xml's version.properties In main pom.xml change the following properties
OOM:
BRMS_DEPENDENCY_VERSION
| https://gerrit.onap.org/r/c/policy/drools-applications/+/104408 |
| 6 - Dependent on policy/drools-applications | policy/engine 1.6.4 (In Progress) | all pom.xml's version.properties BRMSGateway/config.properties BRMSGateway/dependency.json BRMSGateway/src/main/java/org/onap/policy/brms/api/BrmsPush.java BRMSGateway/src/test/resources/config.properties packages/base/src/files/install/servers/brmsgw/config.properties packages/install/src/files/brmsgw.conf In main pom.xml change the following properties
|
...
| Steps for Releasing and branching |
|---|
| 1. Go to latest merged review of repo and comment “stage-release” |
| 2. It will trigger2 Jenkins jobs - stage-master & docker-stage-master |
| 3. Once the jobs are successful, create a yaml filefor releasing maven artifacts firstandraise a review |
4. Once that is merged andbuildis successful, create another container.yaml filefor releasing docker image andraise a review NOTE: Drools-applications will require a 2nd "stage-release" to be done after step 3 due to the way it is built. The docker image requires the java artifacts to be released first, which are packaged into the image. |
| 5. Once that is merged andbuildis successful, goto nexus3.onap.org andverify that the image was released |
| 6. Bump the snapshotversiontonextpatchversionandraise a review - I use this command “mvn versions:set -DnewVersion=2.5.1-SNAPSHOT” |
| 7. Once that is merged andbuildis successful, goto gerrit andcreate a “frankfurt” branch. |
| 8. Once the branch is created, bump the master branch tonext minor versionusing the same maven command andraise a review 9. Finally goto frankfurt branch andchange the .gitreview fileto point to frankfurt asdefault branch andraise the review. |