summaryrefslogtreecommitdiff
path: root/RELEASE_PROCESS.markdown
diff options
context:
space:
mode:
authorJeff McCune <jeff@puppetlabs.com>2011-11-08 14:31:51 -0800
committerJeff McCune <jeff@puppetlabs.com>2011-11-08 14:31:51 -0800
commit86e86089fb41cb6fb2d6b7e358ed2afe0506fbeb (patch)
tree312eb24a1ade9186126a5c8a20ec19769ede194d /RELEASE_PROCESS.markdown
parentf2b637acf66a7fbbd5ec7fccaa5add3472bef7fa (diff)
Add note about semver.org leading v in tags.
James pointed out this was lacking in my release process document. I've added a note about the leading v in the annotated tag as per http://semver.org/
Diffstat (limited to 'RELEASE_PROCESS.markdown')
-rw-r--r--RELEASE_PROCESS.markdown6
1 files changed, 4 insertions, 2 deletions
diff --git a/RELEASE_PROCESS.markdown b/RELEASE_PROCESS.markdown
index 99f4f05..3982c84 100644
--- a/RELEASE_PROCESS.markdown
+++ b/RELEASE_PROCESS.markdown
@@ -14,8 +14,10 @@
* If there are only small minor changes, the patch version may be bumped.
* Update the CHANGELOG
* Update the Modulefile
- * Commit these changes with a message along the lines of "Update CHANGELOG and Modulefile for release"
- * Create an annotated tag with git tag -a X.Y.Z -m 'version X.Y.Z'
+ * Commit these changes with a message along the lines of "Update CHANGELOG and
+ Modulefile for release"
+ * Create an annotated tag with git tag -a vX.Y.Z -m 'version X.Y.Z' (NOTE the
+ leading v as per semver.org)
* Push the tag with git push origin --tags
* Build a new package with puppet-module or the rake build task if it exists
* Publish the new package to the forge