Independent Versioning and Release Process

Consumed API from other projects

ProjectAPI DependencyNotes
Portal1.1.0When portal team releases we will upgrade.
DmaapLinking 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

AAIv11No direct link to any libraries
APP-C
No direct link to any libraries
SO
No direct link to any libraries
VFCNo direct link to any libraries


Published API - These projects use the policy libraries to build their code

ProjectAPINotes
CLAMP1.1.2
DCAEn/aImplemented own python API


Update to the next SNAPSHOT version:

RepoNotesExample Commit(s)
policy/common

all pom.xml's

version.properties

https://gerrit.onap.org/r/#/c/28107/
policy/drools-applications

all pom.xml's

version.properties

https://gerrit.onap.org/r/#/c/28109/

policy/drools-pdp

all pom.xml's

version.properties

https://gerrit.onap.org/r/#/c/28111/

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

https://gerrit.onap.org/r/#/c/28113/

policy/docker

all pom.xml's

version.properties

config/pe/brmsgw.conf

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.

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



  • No labels