summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLamont Granquist <lamont@scriptkiddie.org>2015-02-06 13:39:55 -0800
committerLamont Granquist <lamont@scriptkiddie.org>2015-02-09 14:08:57 -0800
commit25c2ef0b28d1977c8d639138d3dee01b4b8aa88e (patch)
treef57c39fd607958c1a4265fbf23ff61bd6b70d626
parentb4b5c07515cdde5acdf94803760f6043f4b17386 (diff)
downloadchef-25c2ef0b28d1977c8d639138d3dee01b4b8aa88e.tar.gz
clarify that good cookbooks don't use compile_time
-rw-r--r--RELEASE_NOTES.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 0de1b26300..9fc573fcd5 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -110,8 +110,9 @@ subsequent warnings in the chef-client run.
If this setting is changed to 'false' then it will adopt Chef-13 style behavior and will default all chef_gem installs to not run at compile_time by default. This
may break existing cookbooks.
-All existing cookbooks which require compile_time true MUST be updated to be explicit about this setting.
-All existing cookbooks which do not require compile_time true SHOULD be updated to be explicit about this setting.
+* All existing cookbooks which require compile_time true MUST be updated to be explicit about this setting.
+* To be considered high quality, cookbooks which require compile_time true MUST be rewritten to avoid this setting.
+* All existing cookbooks which do not require compile_time true SHOULD be updated to be explicit about this setting.
For cookbooks that need to maintain backwards compatibility a `respond_to?` check should be used: