Versions Compared

Old Version 87

changes.mady.by.user ASF Infrabot

Saved on

compared with

New Version 326

changes.mady.by.user Edward J. Yoon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Table of Contents

...

This page explains related information required for publishing a release.

Check list before release

...

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

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

Building Distribution

  1. Update to the latest SVN revision:
No Format
 svn up

2. Publish a SNAPSHOT

No Format
 mvn deploy

3. Prepare the release Build the Hama distribution:

No Format
 mvn install package [gpg:sign]  release:prepare

If you need to rollback the release,

No Format
 mvn release:rollback

.

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

No Format
gpg --armor --output hama-X.X.X.tar.gz.asc --detach-sig hama-X.X.X.tar.gz 
gpg --verify hama-X.X.X.tar.gz.asc 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

5. Put the release candidate somewhere people can test it on different platforms

No Format

scp dist/target/** edwardyoon@people.apache.org:/home/edwardyoon/public_html/dist/0.6.1-RC3

Voting

Wiki Markup
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\].

...

Publishing

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

  1. Manage versions in JIRA

0. Update Maven settings2. Release artifacts

No Format

<settings>
<servers>
 mvn   <server>
      <id>apache.website</id>
	<username>edwardyoon</username>
	<privateKey>/home/edward/.ssh/id_dsa</privateKey>
	<passphrase>YOUR-PASS</passphrase>
	<directoryPermissions>775</directoryPermissions>
      <filePermissions>644</filePermissions>
   </server>
       <server>
         <id>apache.snapshots.https</id>
         <username>edwardyoon</username>
         <password>YOUR-PASS</password>
       </server>

  <!-- To stage a release of some part of Maven -->
    <server>
      <id>apache.releases.https</id>
      <username>edwardyoon
      </username>
      <password>YOUR-PASS</password>
    </server>

</servers>

  <profiles>
    <profile>
      <id>apache-release</id>
      <properties>
    <gpg.passphrase>YOUR-PASS</gpg.passphrase>
      </properties>
    </profile>
  </profiles>
</settings>
  1. Manage versions in JIRA

2. Release artifacts

3. Website update

No Format

mvn clean site-deploy

4. Move Artifacts into Place

No Format

ssh people.apache.org

cp -r ~/public_html/hama-{$VERSION}-incubating-RC2 /www/www.apache.org/dist/incubator/hama/{$VERSION}-incubating
cd /www/www.apache.org/dist/incubator/hama
chgrp -R incubator {$VERSION}-incubating
chmod -R g+w {$VERSION}-incubating

# remove older versions

...

release:perform

Now you must close the staging repository to indicate to Nexus that the build is done and to make the artifacts available. See http://www.apache.org/dev/publishing-maven-artifacts.html

No Format

scp -r edwardyoon@people.apache.org:/home/edwardyoon/public_html/dist/0.6.2-RC1/ ./
mv 0.6.2-RC1 0.6.2
svn add 0.6.2; svn commit ./ -m "Release Hama 0.6.2"

3. Website update

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

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

5. After release is published to dist, please remove the old release.

Reference