Versions Compared

Old Version 39

changes.mady.by.user Pamela Dragosh

Saved on

compared with

New Version 40

changes.mady.by.user Pamela Dragosh

Saved on

Key

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

...

Code Block
git tag -sm "6.0.0-ONAP Release" 6.0.0-ONAP
git push <remote-name> 6.0.0-ONAP


Steps for Releasing and branching
1. Go to latest merged review of repo and comment “stage-release”
2. It will trigger2 Jenkins jobs - stage-master & docker-stage-master
3. Once the jobs are successful, create a yaml filefor releasing maven artifacts firstandraise a review

4. Once that is merged andbuildis successful, create another container.yaml filefor releasing docker image andraise a review

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

5. Once that is merged andbuildis successful, goto nexus3.onap.org andverify that the image was released 
6. Bump the snapshotversiontonextpatchversionandraise a review - I use this command “mvn versions:set -DnewVersion=2.5.1-SNAPSHOT”
7. Once that is merged andbuildis successful, goto gerrit andcreate a “frankfurt” branch. 
8. Once the branch is created, bump the master branch tonext minor versionusing the same maven command andraise a review 9. Finally goto frankfurt branch andchange the .gitreview fileto point to frankfurt asdefault branch andraise the review.