...

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

...

Update the

...

website

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

...

1. Prepare to edit the website. 

   Code Block
   svn co https://svn

...

1. .apache.org

...

1. /repos/asf/sentry/

   
   

   1. Add the release to the sentry/site/trunk/content/general/downloads.mdtext

   2. Add the release to the sentry/site/trunk/content/general/history.mdtext

   3. Commit the changes
   4. Go to https://cms.apache.org/sentry/  get the sentry working copy, force a new copy if you don't see your changes yet, and then ask it to publish the new copy. That should update the downloads and history page as per the changes you made to downloads.mdtext, history.mdtext earlier. If you don't see it yet, you may have to wait 24 hours - it should be there by then.
2. Update the blog with new features.

Announce the release

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

To: announce@apache.org, dev@sentry.apache.org
Subject: [ANNOUNCE] Apache Sentry X.Y.Z released

The Apache Sentry team is happy to announce the release of version X.Y.Z.
Apache Sentry is a system to enforce fine grained role based authorization
to data and metadata stored on a Hadoop cluster.

The release bits are available at:
http://sentry.apache.org/general/downloads.html

Sentry X.Y.Z Release Notes are available here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314720&version=12343306


We would like to thank all contributors who made the release possible.

Regards,
Sentry team

Update the website

Prepare to edit the website. 

svn co https://svn.apache.org/repos/asf/sentry/

1. Add the release to the sentry/site/trunk/content/general/downloads.mdtext

2. Add the release to the sentry/site/trunk/content/general/history.mdtext

3. Commit the changes
4. Go to https://cms.apache.org/sentry/  get the sentry working copy, force a new copy if you don't see your changes yet, and then ask it to publish the new copy. That should update the downloads and history page as per the changes you made to downloads.mdtext, history.mdtext earlier. If you don't see it yet, you may have to wait 24 hours - it should be there by then.

...

Preparing Branch for Future Maintenance Release

...