From 5ea48ff33f3222791ebfd27801b23f06db5a1436 Mon Sep 17 00:00:00 2001 From: Brendan Forster Date: Mon, 3 Feb 2014 20:34:58 +1100 Subject: [PATCH] added deployment doc --- DEPLOYMENT.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 DEPLOYMENT.md diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md new file mode 100644 index 00000000..213325cb --- /dev/null +++ b/DEPLOYMENT.md @@ -0,0 +1,18 @@ +## 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](https://www.myget.org/feed/Packages/octokit) 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. Push the tag to the server. `git push --tags` +8. Accept the pull request. +9. 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