Difference between revisions of "OpenstackChefStablebranchCreateNotes"
m |
|||
Line 22: | Line 22: | ||
# Decide on new levels of tools (rubocop, foodcritic), we have always be trying to move forward with these | # Decide on new levels of tools (rubocop, foodcritic), we have always be trying to move forward with these | ||
# Changes for each cookbook and repo | # Changes for each cookbook and repo | ||
+ | ## update metadata with new version level | ||
## once infra gate changes are in place to handle it, update Gemfile wtih new levels | ## once infra gate changes are in place to handle it, update Gemfile wtih new levels | ||
## create robocop TODO file to outline that work to be done (rubocop --auto-gen-config and add an inherit_from: .rubocop_todo.yml in your .rubocop.yml) | ## create robocop TODO file to outline that work to be done (rubocop --auto-gen-config and add an inherit_from: .rubocop_todo.yml in your .rubocop.yml) |
Revision as of 15:41, 27 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
- Changes for each cookbook and repo, create a bug to tie all the following branch work together
- update .gitignore to remove both lock files
- update.gitreview to ref defaultbranch=stable/juno
- update Berksfile to ref branch: 'stable/juno'
- create Gemfile.lock then Berks.lock. One way to do this is to simply run "rake unit", then "git add *.lock"
- see https://github.com/stackforge/cookbook-openstack-identity/commit/3a99613b89fb28d21def8cbeaa63e40da32768f5 for example
- Create a review with the above and put it up against the stable/<release> branch.
- Get it merged in and you should be good
Steps for new master branch
Now we have a new master, need to get it in sync with matching base openstack release.
- Possible infra changes for changes to the gates we want for this release
- Decide on new levels of tools (rubocop, foodcritic), we have always be trying to move forward with these
- Changes for each cookbook and repo
- update metadata with new version level
- once infra gate changes are in place to handle it, update Gemfile wtih new levels
- create robocop TODO file to outline that work to be done (rubocop --auto-gen-config and add an inherit_from: .rubocop_todo.yml in your .rubocop.yml)
- update code with refs to old openstack release juno -> kilo (defaults, readme, ...)
- update each conf file with any new base openstack defaults and new/changed sections
- update all code looking for deprecation's that can now be removed
- update and package dependencies that have changed for each component
- update all spec test platforms to targeted levels we want for this release