add RELEASE_NOTES on gem_package source changeslcg/chef-13-rubygems-source

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

1 files changed, 14 insertions, 0 deletions

diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 75852adaf2..4a82994ff2 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -224,3 +224,17 @@ Accessing a provider class is a bit more complex, as you need a resource against
 ```ruby
 Chef::ProviderResolver.new(node, find_resource!("mycook_thing[name]"), :nothing).resolve
 ```
+
+### Rubygems provider sources behavior changed.
+
+The default behavior of the `gem_package` and `chef_gem` resources is now to inherit whatever settings are in the external environment
+that chef is running in.  Chef no longer forces `https://rubygems.org`.  The `Chef::Config[:rubygems_uri]` default has been changed to
+nil.  It can now be set to either a string URI or to an array of string URIs.  The behavior of setting the source on an individual
+resource now overrides the source setting completely and does not inherit the global setting.
+
+Users that previously relied on the source setting always being additive to "https://rubygmes.org" will find that they need to use
+the array form and explicitly add "https://rubygems.org" to their resources.  Users can now more easily remove "https://rubygems.org"
+either globally or on a resource case-by-case basis.
+
+The behavior of the `clear_sources` property is now to only add `--clear-sources` and has no side effects on the source options.
+>>>>>>> add RELEASE_NOTES on gem_package source changes