...

The RM should then send the pointer to the umbrella issue along with the tentative timeline for branch point to the developer lists (TODO: Also send to users list once we create one). Any work identified as release related that needs to be completed should be added as a subtask of the umbrella issue to allow users to see the overall release progress in one place.

To: dev@sentry.incubator.apache.org
Subject: Work on $release release has started

Created a tracking jira (jira#) for the Sentry $release and plan to branch tentatively on $date. 
 
What would you like to see included?
Thanks,
$RM

...

1. Create a release branch

   1. Clone fresh repository copy

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

   2. Checkout master branch

      Code Block
      git checkout master

   3. Check that current HEAD points to commit on which you want to base new  release branch. Checkout particular commit if not.

      Code Block
      git log # Check current branch history. HEAD should point to commit that you want to be base for your release branch git checkout abcdef123 # Check out particular commit that should be base for release branch if -^

   4. Create new release branch with name "branch-$version"

      Code Block
      git checkout -b branch-1.7.0

   5. Update CHANGELOG in the trunk to indicate the changes going into the new version.

      The change list can be swiped from the JIRA release note tool (use the "text" format for the change log). See JIRA Cleanup above to ensure that the release notes generated by this tool are what you are expecting.

   6. Remove -SNAPSHOT from the release branch and commit

      Code Block
      find . -name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.Y.0/" or mvn versions:set -DnewVersion=X.Y.0 -DgenerateBackupPoms=false git add . git commit -m "SENTRY-XXXX: Removing -SNAPSHOT from X.Y release branch"

   7. Check your changes and push new branch to Apache repository

      Code Block
      mvn package -Pdownload-hadoop git push origin branch-1.7.0

   8. Check that branch was correctly propagated to Apache repository.

2. Prepare the trunk for next release (TODO: update change log?)

   Code Block
   git checkout master find . -name pom.xml | xargs sed -i "" -e "s/1.7.0-SNAPSHOT/1.8.0-SNAPSHOT/" or mvn versions:set -DnewVersion=1.8.0-SNAPSHOT -DgenerateBackupPoms=false git add . git commit -m "SENTRY-XXXX: Preparing for sentry 1.8.0 development" git push origin master:master

3. Send an email announcing new branch

    

   No Format
   To: dev@sentry.incubator.apache.org Subject: New release branch 1.7.0 I've just created new release branch for upcoming 1.7.0 release. Please continue committing to master branch as usual. I'll cherry-pick commits to branch-1.7.0 on per needed basis. Thanks, $RM

...

Upload artifacts and all created check sums with signatures to https://dist.apache.org/repos/dist/dev/incubator/sentry

Update KEYS file

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/incubator/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
  
  

...

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

Call for voting on dev list (PPMC)

To: dev@sentry.incubator.apache.org
Subject: [VOTE] Release Sentry version 1.7.0
This is the release of Apache Sentry, version 1.7.0. 
It fixes the following issues: http://s.apache.org/VlU

Source files : https://dist.apache.org/repos/dist/dev/incubator/sentry/sentry-1.2.0/

Tag to be voted on (rc#): https://git-wip-us.apache.org/repos/asf/incubator-sentry/?p=incubator-sentry.git;a=commit;h=<commit-hash-of-the-tag>
Sentry's KEYS containing the PGP key we used to sign the release:
https://people.apache.org/keys/group/sentry.asc (or http://www.apache.org/dist/incubator/sentry/KEYS for non committers)

Note that this is a source only release and we are voting on the source: tag=release-1.2.0, SHA=5e6e34202b26d7d5bc1a41e3dd4ad0cacd123e3f (You can get the hash of the tag by doing "git rev-list release-1.4.0 | head -n 1" )

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Thanks,
$RM 

The vote has to be called first on the dev list. Upon receiving 3 +1s from the PPMC, reply to the voting thread and prefixing [RESULT] to the subject line with the results. 

Example close email:

To: dev@sentry.incubator.apache.org
Subject: [RESULT][VOTE] Release Sentry incubating version 1.2.0
 
Voting is now closed and has passed with the following tally.,

PPMCBinding +11s: Patrick Hunt, Arvind Prabhakar, Andrei Savu
Non binding +1s: Xuefu Zhang, Jarcec Cecho
Others +1:, Ashish Paliwal.

A vote will now be called on general@incubator.apache.orgThanks to everyone who voted! I'll continue with the rest of the release process.
 
$RM

Voting on @general

The vote should be now called on general@incubator.apache.org for IPMC votes. Binding votes are from IPMC member, and non-binding votes are from PPMC members.

To: general@incubator.apache.org
Subject: [VOTE] Release Sentry incubating version 1.2.0
 
This is the first incubator release of Apache Sentry, version
1.2.0-incubating.
 
<Same as above...>

A vote on releasing this package has already passed in Apache Sentry
PPMC[1] including  +1 votes from our PPPMC (XXX, XXX, XXX ...).

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

<RM>

[1] -
http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results

   By convention, vote closing email is sent to general@incubator.apache.org by replying to the voting thread and prefixing [RESULT] to the subject line.  This method keeps the closing email in the same thread with the voting emails for better record keeping in the mail archive.

Example close email:

To: general@incubator.apache.org
Subject: [RESULT][VOTE] Release Sentry incubating version 1.2.0
 
Voting is now closed and has passed with the following tally,

Binding +1s: Patrick Hunt, Arvind Prabhakar, Andrei Savu
Non binding +1s: Xuefu Zhang, Jarcec Cecho, Ashish Paliwal.

Thanks to everyone who voted! I'll continue with the rest of the release process.
 
$RM

Rolling out the Release

Close JIRA version

You need to close the release in JIRA so that everyone knows that your version should not be used as "fixVersion" for new bugs. Go to JIRA "Administer project" page and follow "Versions" in left menu. Table with list of all releases should appear, click on additional menu on the right of your release and choose "Release" option. Submit release date and you're done.

Upload the artifacts

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

svn co https://dist.apache.org/repos/dist/release/incubator/sentry/ sentry-release
cd sentry-release
mkdir 1.2.0-incubating/
cp $source_to_your_artifacts 1.2.0-incubating/
svn add 1.2.0-incubating

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

Announce the release

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

...

Rolling out the Release

...

Close JIRA version

You need to close the release in JIRA so that everyone knows that your version should not be used as "fixVersion" for new bugs. Go to JIRA "Administer project" page and follow "Versions" in left menu. Table with list of all releases should appear, click on additional menu on the right of your release and choose "Release" option. Submit release date and you're done.

Upload the artifacts

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.

svn co https://dist.apache.org/repos/dist/release/sentry/ sentry-release
cd sentry-release
mkdir 1.2.0/
cp $source_to_your_artifacts 1.2.0/
svn add 1.2.0

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,

To: announce@apache.org, dev@sentryincubator/sentry
The change list is available at: http://s.apache.org/VlU
We would like to thank all contributors who made the release possible.

Disclaimer
Apache Sentry is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Subject: [ANNOUNCE] Apache Sentry 1.2.0 released

The Apache Sentry team is happy to announce the release of version 1.2.0. 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

...