Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Consumed API from other projects

...

Release OrderRepo (released version)NotesExample Commit(s) for upgrading versions
1

policy/parent

3.2.0 (TBD)

all pom.xml's

version.properties

https://gerrit.onap.org/r/c/policy/parent/+/

104021

110016

2a

policy/docker

2.1.0 (TBD)1

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
https://gerrit.onap.org/r/c/policy/docker/+/102678114316
2b

policy/common

1.7.1 (TBD)

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
https://gerrit.onap.org/r/c/policy/common/+/104047114285
3

policy/models

2.3.1 (TBD)5

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version


https://gerrit.onap.org/r/c/policy/models/+/104232114286

4a

policy/api

2.3.1 (TBD)3

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/api/+/104257114288
4b

policy/pap

2.3.1 (TBD)3

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/pap/+/104262114290
4c

policy/drools-pdp

1.7.1 (TBD)4

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version

Update policy/drools-applications dockerfile to pull this image (see below)

Update policy/drools-applications files:

  • pom.xml: version.policy.drools-pdp
  • controlloop/common/feature-controlloop-management/src/test/resources/op.pom

https://gerrit.onap.org/r/c/policy/drools-pdp/+/104291114325

4d

policy/apex-pdp

2.4.1 (TBD)4

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/apex-pdp/+/114292
4e

policy/xacml-pdp

2.3.1 (TBD)3

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/xacml-pdp/+/104294114324
4f

policy/distribution

2.4.1 (TBD)3

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/distribution/+/104296114291
5 - Dependent only on policy/drools-pdp

policy/drools-applications

1.7.0 (TBD)5

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
  • version.policy.drools-pdp


https://gerrit.onap.org/r/c/policy/drools-applications/+/104408114862


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.

...

Steps for Releasing and branching

Raise a review to refer released version of dependency (parent, common, models etc.)

Go to latest merged review of repo and comment “stage-release

It will trigger 2 Jenkins jobs - stage-master & docker-stage-master

NOTE: The "docker-stage-master" job will fail for drools-applications

Once the jobs are successful, create a yaml file for releasing maven artifacts first and raise a review.  This file can typically be generated using this script: mkart.sh

Once that is merged and build is successful, create another container.yaml file for releasing docker image and raise a review.  This file can typically be generated using this script: mkdock.sh

NOTE: Drools-applications will require a 2nd "stage-release" to be done due to the way it is built; the docker image requires the java artifacts to be released first, which are packaged into the image.

Once that is merged and build is successful, go to nexus3.onap.org & nexus.onap.org and verify that the image & artifacts were released 

Bump the snapshot version to next patch version and raise a review - Use this command “mvn versions:set -DnewVersion=<snapshot-version>

Update the patch version in "version.properties" file.

Below steps are ONLY needed when we are branching and proceeding to new release
Once that is merged and build is successful, go to gerrit and create a “guilin” branch.

Once the branch is created, bump the master branch to next minor version using the same maven command and raise a review

Finally go to guilin branch and change the .gitreview file to point to guilin as default branch and raise the review.