Guide for new Hama Committers

Please read this page http://www.apache.org/dev/new-committers-guide.html first.

Update Team List

Please feel free to add your name and Apache ID to Team List page

• Update the http://svn.apache.org/repos/asf/hama/trunk/src/site/xdoc/team-list.xml file
• Build the site

  No Format
  mvn site

• Deploy the website (See http://svn.apache.org/repos/asf/hama/site/trunk/ and http://www.apache.org/dev/project-site.html#svnpubsub)
  

Guide for Hama Committers

This page contains guidelines for committers.

Discuss

Every ideas for improvements, new features, and suggestions are recommended to be discussed in polite terms before implementation on the dev@ list, and then its decisions must be listed on our RoadMap page. In simple improvement or bug type issues, you can skip the discussion and report directly on JIRA.

Review

Hama committers should, as often as possible, attempt to review patches submitted by others. Ideally every submitted patch will get reviewed by a committer within a few days. If a committer reviews a patch they've not authored, and believe it to be of sufficient quality, then they can commit the patch, otherwise the patch should be cancelled with a clear explanation for why it was rejected.

...

You may want to add your KEY to http://incubatorwww.apache.org/dist/hama/KEYS

To add your KEY, you can add text to src/site/resources/files/KEYS https://dist.apache.org/repos/dist/release/hama/KEYS (svn) file. and recommend to use a 4096 bit RSA key.

...

If everything is correctly verified, you have to post the result on the vote thread while casting your vote.

Verification Script

You can use a convenient shell script to check the signatures, it takes the release managers apache index file URL as argument (e.g. http://people.apache.org/~edwardyoon/dist/0.6-RC3/).

#!/bin/bash

function check_return {
        RETVAL=$?
        [ $RETVAL -ne 0 ] && exit 1
}

function check_md5 {
	real=`openssl md5 $1 | cut -d ' ' -f2`
	expected=`cat $1.md5 | cut -d ' ' -f1`
	if [ "$real" != "$expected" ]
	then
	    echo "md5 sums mismatch" && exit 1
	else
	    echo "md5 checksums OK"
	fi
}

function check_sha1 {
        real=`openssl sha1 $1 | cut -d ' ' -f2`
        expected=`cat $1.sha1 | cut -d ' ' -f1`
        if [ "$real" != "$expected" ]
        then
            echo "sha1 sums mismatch" && exit 1
        else
            echo "sha1 checksums OK"
        fi
}


function import_keys {
	wget -q http://hama.apache.org/files/KEYS
	gpg --import KEYS
	rm KEYS
}

if [ $# -ne 2 ]
then
  echo "Usage: `basename $0` {people.apache.org index url of the release}"
  exit 1
fi


import_keys

wget --convert-links -q -L -O out.html $1
cat out.html | grep -o -E 'href="([^"#]+).([gz|asc|md5|sha1|zip])"' | cut -d'"' -f2 | sort | uniq > links

mkdir release

while read lnk; do
  echo "Downloading $lnk"
  wget --directory-prefix=release $lnk
done < links

for filename in `find release/ -iregex ".*\(gz\|zip\)" -printf "%f\n"`
do
  echo "checking release/$filename"

  gpg --verify release/$filename.asc  
  check_return
  
  check_md5 release/$filename 

  check_sha1 release/$filename
    
done;

rm out.html
rm links

Eclipse Settings

You should set the Active Maven Profiles property for each of these projects: hama-core, hama-examples, hama-graph and hama-ml