summaryrefslogtreecommitdiff
path: root/ReleaseInstructions
diff options
context:
space:
mode:
authorJaikiran Pai <jaikiran@apache.org>2019-09-05 10:23:13 +0530
committerJaikiran Pai <jaikiran@apache.org>2019-09-05 10:23:13 +0530
commit7a3e9034e1583c319b809e641824a2fc10423f15 (patch)
tree7882cdf10f340e76b2a272bbd7a0255bf0e2d59c /ReleaseInstructions
parent13538807edeb5688fe1879b8cc30a7e582f919b2 (diff)
downloadant-7a3e9034e1583c319b809e641824a2fc10423f15.tar.gz
Clarify the snapcraft release command
Diffstat (limited to 'ReleaseInstructions')
-rw-r--r--ReleaseInstructions8
1 files changed, 6 insertions, 2 deletions
diff --git a/ReleaseInstructions b/ReleaseInstructions
index 6a59b4fb2..191662a35 100644
--- a/ReleaseInstructions
+++ b/ReleaseInstructions
@@ -315,9 +315,13 @@ Note: This document was adapted from the one created in the context of
23. copy the candidate snaps to stable. First figure out the revision
$ snapcraft status ant
- $ snapcraft release ant REVISION latest/stable 1.10/stable
+ $ snapcraft release ant REVISION latest/stable
+ $ snapcraft release ant REVISION 1.10/stable
- where REVISION is the revision you want to promote
+ where REVISION is the revision you want to promote (keep in mind that the
+ REVISION isn't the version you are releasing. snapcraft uses its own separate integer
+ value for the REVISION and this value is listed as the output of the previous
+ "snapcraft status ant" command)
24. wait a few hours for the mirrors to catch up