Difference between revisions of "OpenstackChefStablebranchCreateNotes"
(→Steps to create stable/ branch) |
(→Steps to create stable/ branch) |
||
| Line 3: | Line 3: | ||
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. | 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. | ||
| − | # | + | # Go to [https://review.openstack.org/#/admin/projects/stackforge/cookbook-openstack-compute,branches for each repo] as a core member and create the branch with the SHA you want. |
| + | # To get Gerrit to report to the #openstack-chef channel create the "stable/<release_name>" via [https://github.com/openstack-infra/project-config openstack-infra/project-config] project under: gerritbot/channels.yaml. Something [https://review.openstack.org/#/c/156262/ like this] is an example. You may be required to remove an old branch too, keep this in mind. | ||
# Wait for the Patch to be merged by Infra | # Wait for the Patch to be merged by Infra | ||
| − | # | + | # create Berks.lock, Gemfile.lock, (need a longer list) |
| − | + | # Create a review with the above and put it up against the stable/<release> branch. | |
| − | + | # Get it merged in and you should be good | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 18:23, 18 February 2015
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.
- Go to for each repo as a core member and create the branch with the SHA you want.
- 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.
- Wait for the Patch to be merged by Infra
- create Berks.lock, Gemfile.lock, (need a longer list)
- Create a review with the above and put it up against the stable/<release> branch.
- Get it merged in and you should be good
