HowToRelease

See also http://www.apache.org/dev/release.html

Check list before release

http://www.apache.org/dev/release.html

To verify license headers, use RAT check with following command:

% mvn apache-rat:check

Branching the release candidate

Before release, a branch should have been be created for that release in the form <major>.<minor>. For example:

 
svn copy https://svn.apache.org/repos/asf/hama/trunk https://svn.apache.org/repos/asf/hama/branches/0.2

Building Distribution

Update to the latest SVN revision:

 svn up

2. Prepare the release:

 mvn release:prepare

If you are NOT first time,

 mvn release:rollback

.

3. Digitally sign the distribution hama-X.X.X.tar.gz.

md5sum hama-x.x.x.tar.gz > hama-x.x.x.tar.gz.md5
sha1sum hama-x.x.x.tar.gz > hama-x.x.x.tar.gz.sha1

Voting

Each release must be voted by the PMC on the hama-dev mailing list. Vote threads are indicated by starting the subject line with [VOTE].

For a vote to pass at least three +1 votes are needed. Votes are normally run for 72 hours. When starting the vote, indicate the date and time the vote period ends.

When the vote period ends, tally up the votes and report the final result to the mailing list.

Publishing

Once three PMC members (PPMC and IPMC) have voted for a release, it may be published.

Manage versions in JIRA

2. Release artifacts

3. Website update

Use CMS to deploy web site or commit changes to http://svn.apache.org/repos/asf/hama/site/trunk/ directly

4. Move Artifacts into Place

Commit artifacts to https://dist.apache.org/repos/dist/release/hama/

# remove older versions

5. Announce to announce@apache.org, dev@hama.apache.org, user@hama.apache.org

Page tree