...
| Release Order | Repo (current version) | Notes | Example Commit(s) for upgrading versions |
|---|---|---|---|
| 1 | policy/parent 2.1.0 | all pom.xml's version.properties | |
| 2 | policy/common 1.4.0 | all pom.xml's version.properties | https://gerrit.onap.org/r/#/c/71549/ |
| 3 | policy/models 2.1.0 ? | all pom.xml's version.properties | |
| 4 | policy/api 2.0.0 | all pom.xml's version.properties In main pom.xml change the following properties
| |
| 5 | policy/pap 2.0.0 | all pom.xml's version.properties In main pom.xml change the following properties
| |
| 36a | policy/drools-pdp 1.34.50 | all pom.xml's version.properties policy-management/src/test/resources/echo.pom In main pom.xml consider changing the policy.common.version property:
| |
| 36b | policy/apex-pdp 2.0.4 | all pom.xml's version.properties property version.policy.common in main pom.xml | https://gerrit.onap.org/r/#/c/71562/ |
| 6c | policy/ 4xacml-pdp 2.0.0 | all pom.xml's version.properties property version.policy.common in main pom.xml | |
| 7 | policy/drools-applications 1.4.0 | all pom.xml's version.properties In main pom.xml change the following properties
*NOTE: The drools-pdp and drools-applications must have the same version to support pre-loading of artifacts correctly. | |
| 58 | policy/engine 1.4.0 | 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 In main pom.xml change the following properties
| https://gerrit.onap.org/r/#/c/71570/ |
| 69 | policy/distribution 2.1.0 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/#/c/71575/ |
| 7 (no dependencies, just ordering) | policy/docker (tagged 1.4.0 TBD) | There 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/push-policies.sh ./config/pe/brmsgw.conf: BRMS_DEPENDENCY_VERSION And it should be tagged by the LF release team to ensure consistency. |
...