0.8.2 and forward release notes with Gradle

mkdir 0.8.2_RELEASE
cd 0.8.2_RELEASE/
git clone https://git-wip-us.apache.org/repos/asf/kafka.git kafka_0.8.2-src
cd kafka_0.8.2-src/
git checkout -b 0.8.2 origin/0.8.2

Go to JIRA, select roadmap from left panel, click on "release notes" next to the release version and prepare/format the txt release notes (configure to change from html)

git tag -a 0.8.2.0
git push --tags

Setup a little clean room

git clone https://github.com/stealthly/bootstrap
git checkout -b jdk6 origin/jdk6
vagrant up
vagrant ssh
mkdir apache
cd apache
git clone http://git-wip-us.apache.org/repos/asf/kafka.git kafka
cd kafka
git checkout 0.8.2.0
git log

Now make sure the log commit is the same of the tag you are sending out and that you checked out

cd
mkdir kafka-0.8.2-src
cd kafka-0.8.2-src
cp -r ~/apache/kafka/* .
git status

fatal: Not a git repository (or any of the parent directories): .git

if you did not get this you messed up somewhere please go back.

Now prepare the source (after getting your keys local to the box)

cd ..
tar -zcvf kafka-0.8.2-src.tgz kafka-0.8.2-src/
/vagrant/scripts/sign.sh kafka-0.8.2-src.tgz
( gpg --armor --output kafka-0.8.2-src.tgz.asc --detach-sig kafka-0.8.2-src.tgz
gpg --print-md MD5 kafka-0.8.2-src.tgz > kafka-0.8.2-src.tgz.md5
gpg --print-md SHA1 kafka-0.8.2-src.tgz > kafka-0.8.2-src.tgz.sha1
gpg --print-md SHA512 kafka-0.8.2-src.tgz > kafka-0.8.2-src.tgz.sha2 )
upload the artifacts to where you are staging them
check they are there
exit
vagrant destroy

Setup another clean room

vagrant up
vagrant ssh
download the files you signed and uploaded
gpg kafka-0.8.1-src.tgz.asc
/vagrant/scripts/verify.sh kafka-0.8.1-src.tgz

You should see valid signatures and no errors, if errors go back

Gradle must be installed http://www.gradle.org/installation (ubuntu apt-get http://askubuntu.com/questions/328178/gradle-in-ubuntu)
sudo add-apt-repository ppa:cwchien/gradle
sudo apt-get update
sudo apt-get install gradle
wget wget https://people.apache.org/~etc/candidate/src.tgz
tar -xvf kafka-0.8.2-src.tgz
cd kafka-0.8.2-src
gradle
./gradlew clean
cp your private gradle.properties to ~/.gradle

make sure JDK 6 is installed, setup your gradle.properties correctly (see README.md)

./gradlew releaseTarGzAll
cd core/build/distributions/
/vagrant/scripts/sign.sh kafka_2.9.1-0.8.2.tgz
/vagrant/scripts/sign.sh kafka_2.9.2-0.8.2.tgz
/vagrant/scripts/sign.sh kafka_2.10-0.8.2.tgz
/vagrant/scripts/sign.sh kafka_2.11-0.8.2.tgz

Go drop whatever staging repository may be in the maven repo

If you haven't set up gpg key, set up one using 4096 bit RSA (http://www.apache.org/dev/release-signing.html). Make sure that you public key is upload into one of the public servers (http://www.apache.org/dev/release-signing.html#keyserver).
first set up ~/.gradle.properties like the following. Make sure that you can login to https://repository.apache.org/ with you apache id/passwd. The value for signing.keyId can be found by running "gpg --list-secret-keys --fingerprint". The number after the / in the first line is your signing.keyId.

mavenUrl=https://repository.apache.org/service/local/staging/deploy/maven2
mavenUsername=your-apache-id
mavenPassword=your-apache-passwd
signing.keyId=gpgkey
signing.password=gpg-passphrase
signing.secretKeyRingFile=/Users/your-id/.gnupg/secring.gpg

cd ../../../
./gradlew uploadArchivesAll
Go to https://repository.apache.org/#stagingRepositories, find the uploaded artifacts and close this (don't promote until the vote passes). The artifacts should show up under https://repository.apache.org/content/groups/staging/.

Check sbt

git clone https://github.com/stealthly/scala-kafka
git checkout -b 0.8.2
vagrant up
./gradlew test

Verify:

gpg --import KEYS (KEYS can be obtained from http://kafka.apache.org/KEYS)

gpg --verify foo-1.0.tar.gz.asc foo-1.0.tar.gz

0.8.0 and below with SBT

0) Make sure you are using JDK 6
1) Your Key needs to be signed into the KEYS file http://svn.apache.org/repos/asf/kafka/KEYS
2) clone the repository to kafka-X.Y.Z-src
3) checkout the branch to release if releasing not off trunk
4) java -jar ../../apache-rat-0.8/apache-rat-0.8.jar (forgot to-do this in rc1,2,3 will do before running 4)
5) tag the branch and append (git tag -a releaseVersion) the "release notes" from JIRA
6) git push --tags
7) now get rid of git, rm -fr .git/* && rmdir .git && rm -f .gitignore
8) cd ..
9) tar -czvf kafka-X.Y.Z-src.tgz kafka-X.Y.Z-src/*
10) sign the src

gpg --print-md MD5 kafka_X.Y.Z-src.tgz > kafka_X.Y.Z-src.tgz.md5
gpg --armor --output kafka_X.Y.Z-src.tgz.asc --detach-sig kafka_X.Y.Z-src.tgz
gpg --print-md SHA1 kafka_X.Y.Z-src.tgz > kafka_X.Y.Z-src.tgz.sh1

11) scp kafka_X.Y.Z-src* to a folder on a web server
12) ssh in a virtual machine, been using http://vagrantup.com
13) wget the file
14) tar -xvf kafka-X.Y.Z-src.tgz
15) verify signings and hashes
16) run quick start
17) cd kafka-X.Y.Z-src && ./sbt release-tar
18) sign the binary

gpg --print-md MD5 kafka_2.N.0-X.Y.Z.tar.gz > kafka_2.N.0-X.Y.Z.tar.gz.md5
gpg --armor --output kafka_2.N.0-X.Y.Z.tar.gz.asc --detach-sig kafka_2.N.0-X.Y.Z.tar.gz
gpg --print-md SHA1 kafka_X.Y.Z-src.tgz > kafka_X.Y.Z-src.tgz.sh1
gpg --print-md SHA512 kafka_X.Y.Z-src.tgz > kafka_X.Y.Z-src.tgz.sh2

19) create file RELEASE_NOTES.html

add the html version of release notes
vi RELEASE-NOTES.html
Go to Apache JIRA and click on the version X.Y.Z
(i.e. https://issues.apache.org/jira/browse/KAFKA/fixforversion/12317243)
Click Release Notes

20) upload files to directory for voting
21) ./sbt "++2.8.0 publish"
22) ./sbt "++2.8.2 publish"
23) ./sbt "++2.9.1 publish"
24) ./sbt "++2.9.2 publish"
25) ./sbt "++2.10.1 publish"
26) run https://github.com/mumrah/kafka-ivy and see where we are
27) close nexus staging if everything checks out
28) call VOTE
29) if VOTE failure then DROP staged artifacts from Nexus, if VOTE success then RELEASE artifacts to Maven Central
30) VOTE Succeeded, more to-dos
a) in https://dist.apache.org/repos/dist copy new artifacts into X.Y.Z folder and remove previous releases folder (all older releases are in archive)
b) change site to include the new download link from mirrors and change last release to use archive
c) send ANNOUNCE to apache, users and dev lists