expand release process doc post-release steps, includes pin of Chef Client #722
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -127,10 +127,35 @@ based on the branch you just created. | |
| - [ ] Send an email to the chef and chef-dev mailing lists announcing | ||
| the release with a link to the blog post. | ||
|
|
||
|
|
||
| ## Post Release | ||
|
|
||
| Before the release can be considered complete, the following | ||
| post-release steps must be performed; | ||
|
|
||
| - [ ] in `omnibus/config/projects/chef-server.rb`: | ||
| - [ ] Bump the Chef Server version number for development to the next logical | ||
| version number. | ||
|
There was a problem hiding this comment. Might wanna note that people can just look on |
||
| - [ ] Update chef client to the latest stable chef-client version via | ||
| `override :chef`. This may include updates to major and minor | ||
|
There was a problem hiding this comment. Maybe this is implicit, but we should also override ohai. The default for both of these is to pull from master of chef/chef and chef/ohai and ohai has a circular dependency on the chef repo (to pull chef-config). Only during chef-client releases is there a good guarantee that all the versions agree without random duplicate gems. There was a problem hiding this comment. I'm not actually seeing chef locked atm. Is that coming in a separate PR @marcparadise? |
||
| versions. | ||
| - [ ] Update `override` versions of components that are listed | ||
| with `override` versions to the latest stable patch release | ||
| within the current major.minor version. | ||
| - [ ] in `omnibus/config/software`, update components to latest stable | ||
| patch release within the current major.minor version. | ||
| - [ ] Perform `berks update` in `omnibus/` | ||
| - [ ] Perform `bundle update` in: | ||
| - [ ] `oc-chef-pedant/` | ||
| - [ ] `src/oc-id/` | ||
|
There was a problem hiding this comment. @smith How do you feel about this? |
||
| - [ ] `omnibus/` | ||
| - [ ] Perform `./rebar3 update && ./rebar3 unlock && ./rebar3 upgrade` in: | ||
| - [ ] `bookshelf` | ||
| - [ ] `oc_erchef` | ||
| - [ ] `oc_bifrost` | ||
| - [ ] Submit a post-release PR with these changes and confirm no errors | ||
| in the Travis CI and our internal CI pipeline. Merge after | ||
| review. | ||
|
|
||
| Chef Server is now released and ready for the next round of updates. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super duper nit, but any reason we aren't capitalizing
inhere? (I'm sorry!)