diff options
| author | Tim Smith <tsmith@chef.io> | 2019-06-11 13:20:46 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-11 13:20:46 -0700 |
| commit | 2c527b59743a8d4651b2832e5e596ac2aacc11e4 (patch) | |
| tree | 66d32633a237abe088392686a928b48a13169f0b | |
| parent | 2d8d914facbdb3213c215591160b18ee7c785328 (diff) | |
| download | chef-2c527b59743a8d4651b2832e5e596ac2aacc11e4.tar.gz | |
Update docs/dev/how_to/releasing_chef_infra.md
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
| -rw-r--r-- | docs/dev/how_to/releasing_chef_infra.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/how_to/releasing_chef_infra.md b/docs/dev/how_to/releasing_chef_infra.md index 84ac2201d5..bd42e35572 100644 --- a/docs/dev/how_to/releasing_chef_infra.md +++ b/docs/dev/how_to/releasing_chef_infra.md @@ -4,7 +4,7 @@ 1. Has the version number been bumped for releasing? This can be done by merging in a PR that has the "Expeditor: Bump Version Minor" label applied. 2. Are there any outstanding community PRs that should be merged? Ideally we don't make a community member wait multiple months for a code contribution to ship. Merge anything that's been reviewed. - 3. Are new resource "introduced" fields using the correct version? From time to time we incorrectly merge a PR that has the wrong "introduced" version in a new resource or new resource property. If we added new resources or properties make sure these fields match the version we're about to ship. + 3. Are new resource "introduced" fields using the correct version? From time to time, we incorrectly merge a PR that has the wrong "introduced" version in a new resource or new resource property. If we added new resources or properties, make sure these fields match the version we are about to ship. 4. Have any changes in Ohai been shipped to rubygems? 5. Do we have a build in the `current` channel? If not, you might wanna fix that. |