Jump to: navigation, search

OpenstackChefStablebranchCreateNotes

Revision as of 15:37, 20 February 2015 by Kramvan (talk | contribs) (Added to list of change to make)

Steps to create stable/<release> branch

Awesome! We've decided as a group to create the next stable branch. Here are some steps to remind you on how to do it.

  1. Go to for each repo as a core member and create the branch with the SHA you want.
  2. To get Gerrit to report to the #openstack-chef channel create the "stable/<release_name>" via openstack-infra/project-config project under: gerritbot/channels.yaml. Something like this is an example. You may be required to remove an old branch too, keep this in mind.
  3. Wait for the Patch to be merged by Infra
  4. Changes for each cookbook
    1. update .gitignore to remove both lock files
    2. update.gitreview to ref defaultbranch=stable/juno
    3. update Berksfile to ref branch: 'stable/juno'
    4. create Gemfile.lock then Berks.lock
    5. see https://github.com/stackforge/cookbook-openstack-identity/commit/3a99613b89fb28d21def8cbeaa63e40da32768f5 for example
  5. Create a review with the above and put it up against the stable/<release> branch.
  6. Get it merged in and you should be good