Versions Compared

Old Version 56

changes.mady.by.user Sergio Peña

Saved on

compared with

New Version 57

changes.mady.by.user Kalyan Kalvagadda

Saved on

Key

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

...

No Format
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://www.apache.org/dyn/closer.cgi/sentry
The change list is available at: http://s.apache.org/VlU
We would like to thank all contributors who made the release possible.

Regards,
Sentry team

Update the website

  1. Update

    Prepare to edit the website

    : 

    . 

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


    1. Add the release to

      the downloads

      the sentry/site/trunk/content/general/downloads.mdtext

    2. Add the release to

      the history page
  2. Update the blog with new features.

    1. the sentry/site/trunk/content/general/history.mdtext

    2. Commit the changes
    3. 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.
  4. Update the blog with new features.


Preparing Branch for Future Maintenance Release

After the release has been completed, prepare the branch for the next development cycle.

  1. Check out the release branch with:

    git clone https://git-wip-us.apache.org/repos/asf/sentry.git
    cd sentry

    git checkout branch-X.Y


  2. Increment the version property value in all pom.xml files and add the SNAPSHOT suffix. For example, if the released version was 0.7.0, the new value should be 0.7.1-SNAPSHOT. Please note that the SNAPSHOT suffix is required in order to indicate that this is an unreleased development branch. Use Maven's Versions plugin to do this as follows:

    mvn versions:set -DnewVersion=0.7.1-SNAPSHOT -DgenerateBackupPoms=false


  3. Verify that the build is working with changes.

  4. Commit these changes with a comment "Preparing for X.Y.Z+1 development".

    Update how to release page with your experience (smile)