Add notes on deploying a new release

README.md

@@ -86,3 +86,16 @@ for more details.
 Copyright 2013 GitHub, Inc.
 
 Licensed under the [MIT License](https://github.com/octokit/octokit.net/blob/master/LICENSE.txt)
+
+## Deploying a new release
+
+When we're ready to deploy a new release, we need to do the following steps.
+
+1. Create a branch named `release`.
+2. Update [`ReleaseNotes.md`](ReleaseNotes.md). Note that the format is important as we parse the version out and use that for the NuGet packages.
+3. Push the branch to GitHub and create a pull request. This will kick off the MyGet build of the NuGet package with this new version.
+4. Test!
+5. When you're satisfied with this release, push the package from MyGet to NuGet.
+6. Create a tag `git tag v#.#.#`. For example, to create a tag for 1.0.0 `git tag v1.0.0`
+7. Accept the pull request.
+8. Create a [new release](https://github.com/octokit/octokit.net/releases/new) using the tag you just created and pasting in the release notes you just wrote up

ReleaseNotes.md

@@ -11,5 +11,6 @@
 ### New in 0.1.3 (Released 2013/11/5)
 * New Xamarin Component store versions of Octokit.net
 * New clients for managing assignees, milestones, and tags
-* New clients for managing issues, issue events, and issue comments.
-* New client for managing organization members.
+* New clients for managing issues, issue events, and issue comments
+* New client for managing organization members
+* Fixed bug in applying query parameters that could cause paging to continually request the same page