Versions Compared

Old Version 9

changes.mady.by.user Chris Wilper

Saved on

compared with

New Version 10

changes.mady.by.user Chris Wilper

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Make sure the KEYS file at the root of the source tree has your up to date public code signing key and signatures listed. If you don't yet have a code signing key, see Creating a Code Signing Key. When you are ready, append your key with the following command:

  • (gpg --list-sigs YourKeyID YourKeyId && gpg -a --export YourKeyIDYourKeyId) >> 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:

...

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:

  1. mvn install
  2. mvn 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:

  1. mvn release:rollback -Dusername=YourSVNUsername -Dpassword=YourSVNPassword
  2. svn rm https://fedora-commons.org/svn/root/akubra/tags/akubra-x.yImage Modified

Deploy Artifacts to Staging

This step will sign, checksum, and push all release artifacts (including javadocs and sources) to the staging repository.

  1. Check out the tagged release from subversion and "mvn install" it.
  2. Change back to trunk
  3. mvn release:perform -Darguments="-Dgpg.keyname=YourKeyId -Dgpg.passphrase=YourKeyPassword"

Verify and Promote Staged Artifacts

  1. Log into http://oss.sonatype.org/Image Modified UI, click Staging in the left column, then select the staged repository on the right. It will open below. Right click on it and select Close.
  2. Download and test that the artifacts in staging are exactly as they should be once deployed to central.

If anything is incorrect, right click the staged repository and select "Drop". After the problem is resolved, you can re-deploy the artifacts to staging and verify them again. To re-deploy and an already-tagged release:

...