summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMary Jinglewski <mjinglewski@chef.io>2018-11-19 15:52:01 -0500
committerMary Jinglewski <mjinglewski@chef.io>2018-11-19 15:52:01 -0500
commitbcf36fd7749ea63dc41f25b2ae7f15f6b4de9c10 (patch)
treefb8076e4cf021e37da4fd1ba4183fea4616c5113
parent33d65c30cba255c18293fcf2884fc9c2015f27ef (diff)
downloadchef-bcf36fd7749ea63dc41f25b2ae7f15f6b4de9c10.tar.gz
copyediting
Signed-off-by: Mary Jinglewski <mjinglewski@chef.io>
-rw-r--r--RELEASE_NOTES.md6
1 files changed, 2 insertions, 4 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 913135f569..1db0112b57 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -8,8 +8,7 @@ Chef 15 release notes will be added here as development progresses.
### Package provider allow_downgrade is now true by default
-The behavior of the package provider without any allow_downgrade flag is now to allow downgrades. This will mostly
-affect users of the rpm and zypper package providers.
+A package provider without any `allow_downgrade` flag now will allow downgrades, which is opposite from previous versions. This behavior change will mostly affect users of the rpm and zypper package providers.
```
package "foo" do
@@ -26,8 +25,7 @@ package "foo" do
end
```
-That code is now what is necessary to specify that `foo` must be version `1.2.3` or higher. Note that the yum provider
-supports syntax like `package "foo > 1.2.3"` which is preferred to using allow_downgrade and should be used instead.
+That code is now what is necessary to specify that `foo` must be version `1.2.3` or higher. Note that the yum provider supports syntax like `package "foo > 1.2.3"` which should be used and is preferred over using allow_downgrade.
### Node Attributes deep merge nil values