Versions Compared

Old Version 25

changes.mady.by.user Ralph Goers

Saved on

compared with

New Version 26

changes.mady.by.user Matt Sicker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update preferred gpg key server to one that's still online

...

  1. Make sure you have Java 8 as the default JDK.

  2. Run mvn clean install on the project to make sure it will build cleanly. 

  3. Run mvn -P rat -DskipTests clean verify to verify all the licenses are valid. 

  4. Login to https://repository.apache.org using your ASF credentials. Click on your username in the upper-right-hand corner and click Profile. Make sure your email address is correct. If not, contact Infra to get it corrected. You will be unable to get the necessary notifications until it's corrected. 

  5. Make sure you have a 4096-bit RSA PGP key pair for code signing. The public key should be published in a public repository, preferably httpshttp://sks-keyservers.net/keyserver.ubuntu.com. Also make sure the public key is published to https://www.apache.org/dist/logging/KEYS.

  6. Configure this key as your git signing key for release tags: git config user.signingkey 0x1234567812345678
    1. Make sure your user.name and user.email git config values match the name and email of this GPG key.

  7. Edit ~/.m2/settings.xml to add the corresponding private key and its passphrase to your settings. Also add the Apache Subversion server credentials and Sonatype repository credentials to your settings (this is your ASF credentials). You'll want to blank out the passphrase after each release and fill it back in prior to each release so that it isn't compromised. Alternatively, you can encrypt your passwords with a master password.

...