summaryrefslogtreecommitdiff
path: root/RELEASING.md
diff options
context:
space:
mode:
authorJesse Morgan <jesse@jesterpm.net>2016-04-09 12:40:18 -0700
committerJesse Morgan <jesse@jesterpm.net>2016-04-09 12:40:18 -0700
commitee1ad67ab3d1f23701fb55f63d9952736bcdaae1 (patch)
treec67e52b840e8508dec5bcd85b12e590e79b76174 /RELEASING.md
parentebd41d26884f4a8e9247ea4b2439c4c367e68775 (diff)
Fixing formatting in RELEASING.md
Diffstat (limited to 'RELEASING.md')
-rw-r--r--RELEASING.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/RELEASING.md b/RELEASING.md
index eca79d8..0df4aa5 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -8,26 +8,26 @@ Process
1. Increment the version number appropriately. Use [Semantic Versioning](http://semver.org/).
- VERSION=1.1
- mvn versions:set -DnewVersion=$VERSION
+ VERSION=1.1
+ mvn versions:set -DnewVersion=$VERSION
2. Verify the release to make sure all is well.
- mvn clean verify -P release
+ mvn clean verify -P release
3. Commit and tag the latest release.
- git commit -am "Release $VERSION"
- git tag -a v$VERSION -m "Release $VERSION"
+ git commit -am "Release $VERSION"
+ git tag -a v$VERSION -m "Release $VERSION"
4. Deploy to Sonatype:
- mvn clean deploy -P release
+ mvn clean deploy -P release
5. Push commit and tag to GitHub
- git push origin master
- git push origin v$VERSION
+ git push origin master
+ git push origin v$VERSION
6. Create a new Releases on GitHub. Use the tag you just created and optionally
include a change log. Attach the compiled, sources, and javadoc jar files,
@@ -35,7 +35,7 @@ Process
7. Prepare the master branch for the next release by incrementing the version number.
- VERSION=1.2-SNAPSHOT
- mvn versions:set -DnewVersion=$VERSION
- git commit -am "Incrementing the version to $VERSION"
- git push origin master
+ VERSION=1.2-SNAPSHOT
+ mvn versions:set -DnewVersion=$VERSION
+ git commit -am "Incrementing the version to $VERSION"
+ git push origin master