add a RELEASE_NOTE on /opt/chef wiping

this is certainly worth documenting.

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>

1 files changed, 13 insertions, 1 deletions

diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index a4aca19c26..07b98e247f 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -6,9 +6,21 @@ Chef 15 release notes will be added here as development progresses.
 
 ## Breaking Changes
 
+### Omnibus chef packages now wipe /opt/chef before installation
+
+The intent of this is that on upgrading packages the /opt/chef directory is wiped of any stray `chef_gem` installed gem versions and other
+modifications to /opt/chef that might be preserved and cause issues on upgrades.  Due to technical details with rpm script execution order
+the way this was implemented was that a pre-installation script wipes /opt/chef before every install (done consistently this way on
+every package manager).
+
+This will not affect anyone who is properly managing customizations to /opt/chef via chef recipes itself since they will be installed by
+the new chef-client package.
+
+The package installation emits a message that /opt/chef is being removed to inform the user that this action is taking place.
+
 ### Package provider allow_downgrade is now true by default
 
-We reversed the default behavior to `allow_downgrade true` for our package providers. To override this setting to refuse downgrades, use the `allow_downgrade —false` flag. This behavior change will mostly affect users of the rpm and zypper package providers.
+We reversed the default behavior to `allow_downgrade true` for our package providers. To override this setting to ignore downgrades, use the `allow_downgrade false` flag. This behavior change will mostly affect users of the rpm and zypper package providers.
 
 ```
 package "foo" do