...

If your PGP key is not yet in the project's KEYS file, you need to first add that in. To do this, checkout the KEYS file and update it using the following commands:

...

This will take some time to propagate in which you can continue with the other steps of the release process.

...

• Make sure RCs are hosted @ https://dist.apache.org/repos/dist/dev/sentry
• Should be in format apache-$project-$version.tar.gz 
• Verify Signatures and hashes.  You may have to import the public key of the release manager to verify the signatures. (gpg --recv-key <last8 of public key>)
• git tag matches the released bits (diff -rf)
• Can compile successfully from source
• Verify DISCLAIMER, NOTICE and LICENCE (year etc)
• All files have correct headers (Rat check should be clean - mvn verify)
  
  • Make sure there are no conflicting licenses (TODO: how)
• No jar files or the like in the release
  
  

Running the vote

...

Voting has to be done on dev@sentry.apache.org You can close the vote after voting period expires and you accumulate sufficient votes.

...

In order to release you have to checkout release repository located on https://dist.apache.org/repos/dist/release/sentry/ and add release artifacts there.

...

It may take up to 24 hours for all mirrors to sync up (http://www.apache.org/dyn/closer.cgi/sentry/)

Announce the release

Send an email to announce@apache.org (the from: address must be @apache.org). For example,

...

1. Update the website: 
   1. Add the release to the downloads
   2. Add the release to the history page
2. Update the "News" section in the podling status page.Update the blog with new features.
3. Update how to release page with your experience