Page Comparison

...

1. In Gerrit, create the new branch off the master branch in each repository
2. Check that all the branches have been created correctly

3. On the master branch, run the getReleaseData.sh script to update the pf_release_data.csv file

   Code Block
   language bash
   getReleaseData.sh -l onap

   
   

4. Run the newReleaseSnapshots.sh script to update the snapshot versions on all the repositories and merge the generated commits

   1. For a minor release run the script as follows:

      Code Block
      language bash
      newReleaseSnapshots.sh -l onap -i POLICY-112911

      
      

   2. For a major release run the script with the -m flag as follows:

      Code Block
      language bash
      newReleaseSnapshots.sh -m -l onap -i POLICY-112911

      
      

5. Run the resolveRefs.sh script to update the cross references and base docker images, then merge the generated commits

   Code Block
   language bash
   resolveRefs.sh -l onap -i POLICY-112911

   
   

6. Add the new branch to the JJB job Yaml files in onap/ci-management/jjb/policy so that the Jenkins jobs for the new branch are created.
7. Check out the release branch into a separate tree structure:
     release_name/policy/parent
     release_name/policy/common
     etc.
8. On the release branch, edit the file release_name/policy/parent/docs/conf.py and change all references to master or latest to your release name (these variables are release, version and branch)
9. On the release branch, edit the .gitreview file and change the line defaultbranch=master to defaultbranch=<release_name>, where <release_name> is the name of the new release
10. Raise commits and merge the changes in 7. and 8. above.

...