NO BUG - Skip annotated tags when releasing geckodriver r=me
authorAndreas Tolfsen <ato@sny.no>
Tue, 31 Oct 2017 19:10:15 +0000
changeset 689757 2639461973e707cff3b068ce3e25c9f79d9559f8
parent 689756 9d884d70d5494fff4c4a544af8972a2a9b5a019a
child 689758 90ec11e9979144725a796e60905367488fcf4d3b
child 690146 f88bc16ac48818fd8cf35f04e56919c47e786a47
push id87097
push userdholbert@mozilla.com
push dateTue, 31 Oct 2017 22:39:07 +0000
reviewersme
milestone58.0a1
NO BUG - Skip annotated tags when releasing geckodriver r=me DONTBUILD MozReview-Commit-ID: CIX5O9P11Xz
testing/geckodriver/doc/Releasing.md
--- a/testing/geckodriver/doc/Releasing.md
+++ b/testing/geckodriver/doc/Releasing.md
@@ -154,23 +154,19 @@ Now commit all the changes you have made
 As indicated above, the changes you make to this branch will not
 be upstreamed back into mozilla-central.  It is merely used as a
 staging ground for pushing builds to Travis.
 
 
 Tag the release
 ---------------
 
-Run the following command:
-
-	% git tag -a 'vX.Y.Z'
+Run the following command to tag the release:
 
-Write the following in the annotation:
-
-	Tagging release vX.Y.Z
+	% git tag 'vX.Y.Z'
 
 
 Make the release
 ----------------
 
 geckodriver is released and automatically uploaded from Travis by
 pushing a new version tag to the _release_ branch: