...
- Write access to the Akubra subversion git repository hosted at fedora-commons.org. This requires an administrator to add you to the akubra-committer LDAP groupat https://github.com/akubra/akubra.
- Write access to the org.akubraproject groupId in the snapshot and staging repositories hosted at oss.sonatype.org. If you don't already have this, you will need to:
- Sign up for a Sonatype OSS account
- Ask the previous release manager to request authorization for this account via the Akubra Project Hosting Ticket
- The login details for the fcrelman account at fedora-commons.org. This is only required for official releases, not snapshots. If you don't have this information yet, you can get it from the previous release manager.
...
(gpg --list-sigs YourKeyId && gpg -a --export YourKeyId) >> KEYS
Do a Dry Run
This step is not required, but performs a useful sanity check without committing any changes. From a clean, up-to-date copy of trunk, run the following command:
mvn release:prepare -DdryRun=true
Tag and Increment Version
Stage the Release
This step will set the version declared in the project's pom.xml files, commit the changes to trunkgit, tag the release, and finally, check in another trunk commit and push andother change that increments the next development version (e.g. x.y-SNAPSHOT) in the pom.xml files.
| No Format |
|---|
mvn |
...
Note: This may fail to compile part way through the process, complaining that an internal project dependency is not met. If this occurs, don't worry. Just run the following:
mvn installmvn release:prepare -Dusername=YourSVNUsername -Dpassword=YourSVNPassword
If backing out of this step is needed for any reason, the following will restore the subversion repository and your working copy to the state it was previously in:
mvn release:rollback -Dusername=YourSVNUsername -Dpassword=YourSVNPasswordsvn rm https://fedora-commons.org/svn/root/akubra/tags/akubra-x.y
Deploy Artifacts to Staging
This step will sign, checksum, and push all release artifacts (including javadocs and sources) to the staging repository.
...
release:clean
mvn release:prepare -Dtag=v0.3.1
# If the above fails due to missing dependencies,
# run it again after first running 'mvn install'
git pull
git checkout v0.3.1
mvn clean install
git checkout master
mvn release:perform
|
Verify and Promote Staged Artifacts
...
mvn release:perform -Dtag=akubra-x.y -DconnectionUrl=scm:svn:https://fedora-commons.org/svn/root/akubra -Darguments="-Dgpg.keyname=YourKeyId -Dgpg.passphrase=YourKeyPassword"v0.3.1
If everything looks good, right click on the repository and select "Promote". The artifacts should be synced to central within an houra few hours.
Upload Static Documentation
...