Wipe the 12.16 release notes out

We merged in a 12.17 change into the 12.16 notes.

Signed-off-by: Tim Smith <tsmith@chef.io>

1 files changed, 3 insertions, 141 deletions

diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index d3c492ea35..56191bae74 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,11 +1,10 @@
-*This file holds "in progress" release notes for the current release under development and is intended for consumption by the Chef Documentation team.
-Please see [https://docs.chef.io/release_notes.html](https://docs.chef.io/release_notes.html) for the official Chef release notes.*
+_This file holds "in progress" release notes for the current release under development and is intended for consumption by the Chef Documentation team. Please see <https://docs.chef.io/release_notes.html> for the official Chef release notes._
 
-# Chef Client Release Notes 12.16:
+# Chef Client Release Notes 12.17:
 
 ## Highlighted enhancements for this release:
 
-* Added msu_package resource and provider which supports the installation of Microsoft Update(MSU) packages on Windows. Example:
+- Added msu_package resource and provider which supports the installation of Microsoft Update(MSU) packages on Windows. Example:
 
   ```ruby
   msu_package 'Install Windows 2012R2 Update KB2959977' do
@@ -30,141 +29,4 @@ Please see [https://docs.chef.io/release_notes.html](https://docs.chef.io/releas
   end
   ```
 
-### `attribute_changed` event hook
-
-* Added `attribute_changed` event hook:
-
-In a cookbook library file, you can add this in order to print out all attribute changes in cookbooks:
-
-```ruby
-Chef.event_handler do
-  on :attribute_changed do |precedence, key, value|
-    puts "setting attribute #{precedence}#{key.map {|n| "[\"#{n}\"]" }.join} = #{value}"
-  end
-end
-```
-
-If you want to setup a policy that override attributes should never be used:
-
-```ruby
-Chef.event_handler do
-  on :attribute_changed do |precedence, key, value|
-    raise "override policy violation" if precedence == :override
-  end
-end
-```
-
-There will likely be some missed attribute changes and some bugs that need fixing (hint: PRs accepted), there could be
-added command line options to print out all attribute changes or filter them (hint: PRs accepted), or to add source
-file and line numbers to the event (hint: PRs accepted).
-
-### Automatic connection to Chef Automate's Data Collector with supported Chef Server
-
-Chef Client will automatically attempt to connect to the Chef Server
-authenticated data collector proxy. If you have a supported version of
-Chef Server and have enabled this feature on the Chef Server, Chef
-Client run data will automatically be forwarded to Automate without
-additional Chef Client configuration. If you do not have Automate or the
-feature is disabled on the Chef Server, Chef Client will detect this and
-disable data collection.
-
-Note that Chef Server 12.11.0+ (not yet released as of the time this was
-written) is required for this feature.
-
-### RFC018 Partially Implemented: Specify `--field-separator` for attribute filtering
-
-If you have periods (`.`) in your Chef Node attribute keys, you can now pass
-the `--field-separator` (or `-S`) flag along with your `--attribute` (or `-a`)
-flag to specify a custom nesting character other than `.`.
-
-In a situation where the *webapp* node has the following node data:
-```json
-{
-  "foo.bar": "baz",
-  "alpha": {
-    "beta": "omega"
-  }
-}
-```
-
-Running `knife node show` with the default field separator (`.`) won't show
-us the data we're expecting for some attributes:
-
-```shell
-$ knife node show webapp -a foo.bar
-webapp:
-  foo.bar:
-
-$ knife node show webapp -a alpha.beta
-webapp:
-  alpha.beta: omega
-```
-
-However, by specifying a field separator other than `.` we're now able to show
-the data.
-
-```shell
-$ knife node show webapp -S: -a foo.bar
-webapp:
-  foo.bar: baz
-
-$ knife node show webapp -S: -a alpha:beta
-webapp:
-  alpha:beta: omega
-```
-
-### Package locking for Apt, Yum, and Zypper
-
-To allow for more fine grained control of package installation the `apt_package`,
-`yum_package`, and `zypper_package` resources now support the `:lock` and `:unlock` actions.
-
-```ruby
-package "httpd" do
-  action :lock
-end
-
-package "httpd" do
-  action :unlock
-end
-```
-
-### `powershell_package` resource
-
-* Added powershell_package resource and provider which supports installation of packages through Powershell Package Manager
-
-  ```ruby
-  powershell_package 'xCertificate' do
-    action :install
-    version "1.1.0.0"
-  end
-
-  powershell_package 'Install Multiple Packages' do
-    action :install
-    package_name ['xCertificate','xNetworking']
-    version ["2.0.0.0","2.12.0.0"]
-  end
-
-  powershell_package 'Install Multiple Packages' do
-    action :install
-    package_name ['xCertificate','xNetworking']
-    version [nil,"2.12.0.0"]
-  end
-
-  powershell_package 'Install Multiple Packages' do
-    action :install
-    package_name ['xCertificate','xNetworking']
-  end
-
-  powershell_package ['xCertificate','xNetworking'] do
-    action :remove
-    version ["2.0.0.0","2.12.0.0"]
-  end
-
-  powershell_package 'xCertificate' do
-    action :remove
-  end
-  ```
-
-For using powershell_package resource, Administrative access is required and source needs to be already added in Powershell Package Manager using `Register-PackageSource` command
-
 ## Highlighted bug fixes for this release: