summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2019-06-11 13:20:13 -0700
committerGitHub <noreply@github.com>2019-06-11 13:20:13 -0700
commit5b5b10cbeefc219ec92525eb2bbab85fbd221804 (patch)
treeac5f034d9572634b35b2145e036b355a83a3ff4a /docs
parent216187aaf583201fb2feb38975d6a935a284f24a (diff)
downloadchef-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>
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/how_to/releasing_chef_infra.md2
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