Beta for master

hokaccha · Jul 31, 2017 · 4bec89a · 4bec89a
1 parent 9ae7ff3
commit 4bec89a
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/app/package.json b/app/package.json
@@ -3,7 +3,7 @@
   "productName": "GitHub Desktop",
   "bundleID": "com.github.GitHubClient",
   "companyName": "GitHub, Inc.",
-  "version": "0.7.1",
+  "version": "0.7.2-beta0",
   "main": "./main.js",
   "repository": {
     "type": "git",

diff --git a/changelog.json b/changelog.json
@@ -1,6 +1,6 @@
 {
   "releases": {
-    "0.7.2": [],
+    "0.7.2-beta0": [],
     "0.7.1": [
       "[Improved] Redesigned error and warning dialogs to be clearer - #2277",
       "[Improved] Create Pull Request dialog shows more feedback while it's working - #2265",

diff --git a/docs/process/releasing-updates.md b/docs/process/releasing-updates.md
@@ -17,7 +17,7 @@ We have three channels to which we can release: `production`, `beta`, and `test`
 1. Commit & push the changes.
 1. Run `.release! desktop/YOUR_BRANCH to {production|beta|test}`.
   * We're using `.release` with a bang so that we don't have to wait for any current CI on the branch to finish. This might feel a little wrong, but it's OK since making the release itself will also run CI.
-1. If you're releasing a production update, release a beta update too so that beta users are on the latest release as well.
+1. If you're releasing a production update, release a beta update for the next version too, so that beta users are on the latest release.
 
 ## Error Reporting