...
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/23587/ |
| policy/drools-applications | all pom.xml's version.properties controlloop/packages/basex/src/files/bin/create-cl-amsterdam ??? | |
| policy/drools-pdp | 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/brmsInterface/BRMSPush.java BRMSGateway/src/test/resources/config.properties | |
| policy/docker | all pom.xml's version.properties config/pe/brmsgw.conf | https://gerrit.onap.org/r/#/c/23651/ |
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.
If this is not done, then one should specify the branch when submitting the git review. 'git review amsterdam'
| Code Block |
|---|
[gerrit]
host=gerrit.onap.org
port=29418
project=policy/engine.git
defaultbranch=amsterdam |