summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Keiser <john@johnkeiser.com>2016-08-08 12:01:57 -0700
committerJohn Keiser <john@johnkeiser.com>2016-08-10 14:50:45 -0700
commit88dfc312b3686a3ca9305d10ec1090cd5973c6d0 (patch)
tree1fc4ede2d49f7fa647dfe9aacd3c180dbbb60785
parent9860fd5e3edbda739670a2d24ccb1c9845a0cbf1 (diff)
downloadchef-88dfc312b3686a3ca9305d10ec1090cd5973c6d0.tar.gz
Clear DOC_CHANGES (empty for 12.13)
-rw-r--r--DOC_CHANGES.md13
1 files changed, 1 insertions, 12 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md
index 069cdc62b4..fadd382cbb 100644
--- a/DOC_CHANGES.md
+++ b/DOC_CHANGES.md
@@ -6,15 +6,4 @@ Example Doc Change:
Description of the required change.
-->
-## Doc changes for Chef 12.11
-
-### RFC 062 Exit Status Support
-
-Starting with Chef Client 12.11, there is support for the consistent, standard exit codes as defined in [Chef RFC 062](https://github.com/chef/chef-rfc/blob/master/rfc062-exit-status.md).
-
-With no additional configuration when Chef Client exits with a non-standard exit code a deprecation warning will be issued advising users of the upcoming change in behavior.
-
-To enable the standardized exit code behavior, there is a new setting in client.rb. The `exit_status` setting, when set to `:enabled` will enforce standarized exit codes. In a future release, this will become the default behavior.
-
-If you need to maintain the previous exit code behavior to support your current workflow, you can disable this (and the deprecation warnings) by setting `exit_status` to `:disabled`.
-
+## Doc changes for Chef 12.13