Page History

...

1. Create a release branch

   1. Clone fresh repository copy

      Code Block
      git clone https://git-wip-us.apache.org/repos/asf/incubator-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.2.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.2.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.2.0-SNAPSHOT/1.3.0-SNAPSHOT/" or mvn versions:set -DnewVersion=1.3.0-SNAPSHOT -DgenerateBackupPoms=false git add . git commit -m "SENTRY-XXXX: Preparing for sentry 1.3.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.2.0 I've just created new release branch for upcoming 1.2.0 incubating release. Please continue committing to master branch as usual. I'll cherry-pick commits to branch-1.2.0 on per needed basis. 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. 

Voting is now 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.

PPMC +1: Patrick Hunt, Arvind Prabhakar,Xuefu Zhang, Jarcec Cecho
Others +1: Ashish Paliwal

A vote will now be called on general@incubator.apache.org.
 
$RM

...

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

...

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

...