summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2019-06-11 13:20:05 -0700
committerGitHub <noreply@github.com>2019-06-11 13:20:05 -0700
commit216187aaf583201fb2feb38975d6a935a284f24a (patch)
treed9b554d7f04ddfe62c4eca647806f3f1fcab7b4d /docs
parentc5fd2247d295f0213581763228f3388bdb0e0ce5 (diff)
downloadchef-216187aaf583201fb2feb38975d6a935a284f24a.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 01e6567dc4..3e017f2cf5 100644
--- a/docs/dev/how_to/releasing_chef_infra.md
+++ b/docs/dev/how_to/releasing_chef_infra.md
@@ -1,6 +1,6 @@
# Releasing Chef Infra
-## Validate we're ready to ship
+## Steps to validate that we are ready to ship
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.