-
Notifications
You must be signed in to change notification settings - Fork 90
Release Process
Colin Decker edited this page May 17, 2016
·
3 revisions
This outlines the basic process for doing a release.
- Maven installed on your machine
- Key pair generated with gpg, with the public key registered with several key servers
- Can generate with
gpg --gen-key
and export withgpg --armor --export <your-email>
- Can generate with
- Access to deploy to the
com.google.code.java-allocation-instrumenter
group on Maven Central- Requires an account on oss.sonatype.org
- Maven needs to be able to authenticate with oss.sonatype.org
- Find your Access Token by logging into oss.sonatype.org, finding your profile and clicking "Access Token" in the dropdown menu
- Create or edit
~/.m2/settings.xml
. Inside<settings><servers>
, add the<server>
element from the User Token popup. Replace<id>${server}</id>
with<id>sonatype-nexus-staging</id>
git checkout master
git pull
mvn clean install
git checkout -b release<version>
mvn versions:set versions:commit -DnewVersion=<version>
git commit -am 'Set release version number'
git tag java-allocation-instrumenter-<version>
git push --tags
mvn clean source:jar javadoc:jar deploy -Dgpg.skip=false
If you have more than one gpg key, you'll also need -Dgpg.keyname=<keyname>
.
- Browse to https://oss.sonatype.org/index.html#stagingRepositories
- Select the staged repository
- Click on "Close", accept at prompt, refresh and wait for close to finish
- Click on "Release", accept at prompt
- Edit
README.md
to update the latest release number - (Optional) Edit the Github release info page (e.g. 3.0.1) to add release notes and/or add the released bytecode, source and Javadoc jars
You can now delete the release branch since the released commit has a tag:
git checkout master
git branch -D release<version>