diff options
| author | Tim Smith <tsmith@chef.io> | 2019-06-11 13:20:13 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-11 13:20:13 -0700 |
| commit | 5b5b10cbeefc219ec92525eb2bbab85fbd221804 (patch) | |
| tree | ac5f034d9572634b35b2145e036b355a83a3ff4a | |
| parent | 216187aaf583201fb2feb38975d6a935a284f24a (diff) | |
| download | chef-5b5b10cbeefc219ec92525eb2bbab85fbd221804.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 3e017f2cf5..dfb9279fd5 100644 --- a/docs/dev/how_to/releasing_chef_infra.md +++ b/docs/dev/how_to/releasing_chef_infra.md @@ -6,7 +6,7 @@ 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. 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. + 5. Do we have a build in the `current` channel? If not, you might wanna fix that. ## Prepare the Release |