Merge pull request #80 from WordPress/release/2.0.0

Release version 2.0.0

Author: aaronjorbin

README.md

@@ -95,6 +95,4 @@ Please follow the [WordPress coding standards](https://make.wordpress.org/core/h
 - 0.4.1 - Remove Mocha as a peerdendency
 - 0.4.2 - set `cmd-diff` to `diff` for svn
 - 1.0.0 - Add filemapping option. Bump minimum node version. Change code style. Update tooling.
-
-### Unreleased
-- Bump minimium node version to 10.
+- 2.0.0 - Bump minimum node version. Use @wordpress/scripts. Allow Credentials to be stored. Reduce Dependancy on Grunt. 

RELEASING.md

@@ -0,0 +1,25 @@
+# Releasing updates
+
+## Manual Testing
+
+Due to the interactive nature of grunt-patch-wordpress, some manual testing is required in order to release a new version. This describes the bare minimum of testing needed to release a new version. 
+
+1) Open a ticket on WordPress Core Trac for the new version. This ticket will serve as both the test bed and for actually updating grunt-patch-wordpress.
+2) Use `npm link` to test the unreleased version of grunt-patch-wordpress
+3) Create a patch in WordPress to bump grunt-patch-wordpress and upload it using `npm run grunt upload_patch`.
+4) Revert that file.
+5) Use `npm run grunt patch` to check the file you just uploaded
+
+## Major, Minor, or Patch
+
+Major: Something is different
+Minor: Something is new
+Patch: Something is fixed
+
+Changing the minimum node version is a major version change 
+
+## Update the Numbers/Docs 
+
+1) Bump `package.json`
+2) Update Readme with new version
+3) When pushing to WordPress Core, give props to everyone who contributed to grunt-patch-wordpress

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "grunt-patch-wordpress",
-	"version": "1.0.0",
+	"version": "2.0.0",
 	"description": "Patch your core WordPress",
 	"author": {
 		"name": "Aaron Jorbin",