-
Notifications
You must be signed in to change notification settings - Fork 1
Making a release
Harry Cummings edited this page Jul 19, 2014
·
10 revisions
Assuming you're working against x.y.0-SNAPSHOT
- Make sure your working checkout is clean and up-to-date with origin/master
- Verify that the build is passing on the CI server
- Update working version to release version:
- Change POM version from
x.y.0-SNAPSHOT
tox.y.0
- Change
JARSPEC_VERSION
env variable in.travis.yml
fromx.y.0-SNAPSHOT
tox.y.0
- Change release version in readme from
x.(y-1).0
tox.y.0
- Change POM version from
- Perform the release
- Make sure you have suitable OSSRH credentials in your maven settings
- Make sure
gpg --list-keys
includes a suitable key pair- The public key must be pushed to OpenPGP keyservers
- You can specify which key to use by setting
default-key
in~/.gnupg/gpg.conf
mvn clean deploy -P release
- Commit and tag the released code
- Commit and push master as normal
git tag x.y.0
git push origin --tags
- Update working version
- Change POM version from
x.y.0
tox.(y+1).0-SNAPSHOT
- Change
JARSPEC_VERSION
env variable in.travis.yml
to match - Change site links in readme from
x.y.0-SNAPSHOT
tox.(y+1).0-SNAPSHOT
- Update site links in wiki from
x.y.0
tox.(y+1).0
- Change POM version from
- Commit and push master as normal