Policy R1 Amsterdam Independent Versioning And Release Process Plan
- Pamela Dragosh
Independent Versioning and Release Process
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
Portal | 1.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 |
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.1.2 | |
DCAE | n/a | Implemented own python API |
Update to the next SNAPSHOT version:
Repo | Notes | Example Commit(s) |
|---|---|---|
policy/common | all pom.xml's version.properties | |
policy/drools-applications | all pom.xml's version.properties | |
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 |
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'
[gerrit]
host=gerrit.onap.org
port=29418
project=policy/engine.git
defaultbranch=amsterdam