From 89e1ded16123fb93db37f4eae4e0babc7fbccf71 Mon Sep 17 00:00:00 2001 From: "Isaac A. Murchie" Date: Thu, 25 May 2017 15:19:59 -0700 Subject: [PATCH] Fix release instructions Fix the actual command for tagging. Mention `appium-desktop` in preference to appium.app/.exe. --- docs/en/contributing-to-appium/developers-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/contributing-to-appium/developers-overview.md b/docs/en/contributing-to-appium/developers-overview.md index 48e4c56ce..569563242 100644 --- a/docs/en/contributing-to-appium/developers-overview.md +++ b/docs/en/contributing-to-appium/developers-overview.md @@ -180,12 +180,12 @@ checked in to GitHub along with changes to `package.json`. 0. Determine whether we have a patch (bugfix), minor (feature), or major (breaking) release according to the principles of SemVer. 0. Update `package.json` with the appropriate new version. 0. Update the CHANGELOG/README with appropriate changes and submit for review as a PR, along with shrinkwrap and `package.json` changes. Wait for it to be merged, then pull it into the release branch. -0. Create a tag of the form `v` on the release branch (usually a minor branch like `1.5` or `1.4`), with: `git tag -a v`, e.g., `git tag -a 1.5.0`. This is not necessary for beta versions. +0. Create a tag of the form `v` on the release branch (usually a minor branch like `1.5` or `1.4`), with: `git tag -a v`, e.g., `git tag -a v1.5.0`. This is not necessary for beta versions. 0. Push the tag to upstream: `git push --tags ` 0. Install dev dependencies (or at least `gulp` and `appium-gulp-plugins`). 0. Run `npm publish` (with `--tag beta` if this isn't an official release). 0. Update the docs at appium.io. Check out the appium.io repo from github, check out the `gh-pages` branch and pull latest. Run `rake publish`. 0. Create a new release on GitHub: go to `https://github.com/appium/appium/releases/tag/v` and hit "Edit Tag". Make the release name `` (e.g., `2.0.5`), then paste in the changelog (but not the changelog header for this version). If it's a beta release, mark as pre-release. 0. Create a new post on discuss.appium.io announcing the release. Post it in the "News" category. Paste in the changelog and any choice comments. Pin it and unpin the previous release post. -0. Notify Appium.app and Appium.exe of the new build so that new GUIs can be released. +0. Begin process of releasing `appium-desktop`. 0. Notify @jlipps to so he can tweet a link to the discuss post.