This document describes how to release Apache Kafka from trunk. 

It is a work in progress and should be refined by the Release Manager (RM) as they come across aspects of the release process not yet documented here.

NOTE: For the purpose of illustration, this document assumes that the version being released is 0.9.0 and the following development version will become 0.10.0.

Prerequisites

• Prepare release plan in the wiki, notifying the community the overall plan and goals for the release (For example: Release Plan 0.10.0)

• Vote on release plan: Release manager should start a vote in dev@kafka.apache.org, asking the community to approve the release plan. 

To: dev@kafka.apache.org
Subject: [VOTE] Release plan - Kafka 0.10.0

We are starting the process to prepare for Kafka $release release. I have created release plan ($link) to cover the tasks under this release.

If you have any JIRA in progress and would like to include it in this release, please follow the process to do so.

Feel free to comment on the JIRA if you have any comments/suggestions.

Thanks,
$RM

• Go over JIRA for the release and make sure that blockers are marked as blockers and non-blockers are non-blockers. This JIRA filter may be handy:

  project = KAFKA AND fixVersion = 0.10.0.0 AND resolution = Unresolved AND priority = blocker ORDER BY due ASC, priority DESC, created ASC

• It is important that between the time that the release plan is voted to the time when the release branch is created, no experimental or potentially destabilizing work is checked into the trunk. While it is acceptable to introduce major changes, they must be thoroughly reviewed and have good test coverage to ensure that the release branch does not start of being unstable. If necessary the RM can discuss if certain issues should be fixed on the trunk in this time, and if so what is the gating criteria for accepting them.

Cut Branches

Create Release Artifacts

• mkdir 0.9.0.0_RELEASE

• cd 0.9.0.0_RELEASE/

• git clone https://git-wip-us.apache.org/repos/asf/kafka.git kafka

• cd kafka

• git checkout -b 0.9.0 origin/0.9.0

Check NOTICE and LICENSE files

• Make sure the NOTICE file has the correct year

Update version number

• If the code is still using a -SNAPSHOT version, remove it and commit the release version. (This will only happen during the first release candidate currently.)

Prepare release notes

• Go to JIRA, move all unresolved jiras with "Fix versions" of 0.9.0.0 to future releases.
• 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). The text version shows up at the bottom of the page.

Prepare the release tag

• git tag -a 0.9.0.0

• git push --tags

  
  

• cd core/build/distributions/
• /vagrant/scripts/sign.sh kafka_2.10-0.9.0.0.tgz
• /vagrant/scripts/sign.sh kafka_2.11-0.9.0.0.tgz

Prepare java and scala docs.

• copy the javadoc and scaladoc directories over

Expose all the binary artifacts, release notes, java and scala doc through an URL

• The easiest way is to sftp them over to home.apache.org/public_html using your apache id (in sftp, first create kafka-0.9.0.0-candidate1, then put -r localDir kafka-0.9.0.1-candidate1).

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 your public key is uploaded to one of the public servers (http://www.apache.org/dev/release-signing.html#keyserver). Also, add your public key to https://github.com/apache/kafka-site/blob/asf-site/KEYS
• Set up ~/.gradle.properties like the following. Make sure that you can login to  https://repository.apache.org/ with your 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=your-gpgkeyId
              signing.password=your-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/.

Voting:

• Send out a voting email to users@kafka.apache.org, dev@kafka.apache.org, kafka-clients@googlegroups.com. In the email, include the git revision next to the git tag (since tag will be dropped when rolling out a new RC).

Verify for voting:

• 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
• Test at least quickstart and unit tests for all scala versions.

If need to roll a new RC

• Go to https://repository.apache.org/#stagingRepositories, find the uploaded artifacts and drop this.
• Drop the git tag for the release.
• Go back to the beginning.

 Post vote todo (after the vote passes):

• Upload all artifacts, release notes, and docs to https://dist.apache.org/repos/dist/release/kafka (an svn repo, using Apache committer id/passwd)
• Go to https://repository.apache.org/#stagingRepositories, find the uploaded artifacts and release this (this will push to maven central)
• Wait for about a day for the artifacts to show up in apache mirror and maven central.
• Send out an announcement email. You will need to use your apache email address to send out the email (otherwise, it won't be delivered to announce@apache.org).
  • Log into people.apache.org with your apache id.
  • Include a paragraph in the announcement email like: "According to git shortlog <number_of_contributors> people contributed to this release: <contributors>" where:
    • number_of_contributors is determined via `git shortlog -sn --no-merges <previous_release_tag>..<current_release_tag> | wc -l` (eg `git shortlog -sn --no-merges 0.8.2.2..0.9.0.0 | wc -l`)
    • contributors is determined via: `git shortlog -sn --no-merges <previous_release_tag>..<current_release_tag> | cut -f2 | tr '\n' ',' | sed -e 's/,/, /g'` (eg `git shortlog -sn --no-merges 0.8.2.2..0.9.0.0 | cut -f2 | sort --ignore-case | tr '\n' ',' | sed -e 's/,/, /g'`)
  • cat mail.txt|mail -s "[ANNOUCE] ..."  announce@apache.org, users@kafka.apache.org, dev@kafka.apache.org, kafka-clients@googlegroups.com
• Add the release data to https://reporter.apache.org/addrelease.html?kafka (must be a Kafka PMC member)
  
  

  Website update process:

  For new releases:

• Git clone https://git-wip-us.apache.org/repos/asf/kafka-site.git
• checkout the branch asf-site
• The releaseTarGzAll target should auto-generate the configuration docs for broker/producer/consumer in ./core/build/distributions/kafka_2.10-0.9.0.0-site-docs.tgz. Untar the file in 090/.
• Copy release javadoc to newly 090/.
• Update documentation.html to include the new documentation link (090/documentation.html).
• Update protocol.html to include the new protocol guide link (090/protocol.html).
• Update downloads.html to include the new download links from mirrors and change last release to use archive.
• Mark the version as released in Kafka JIRA (from JIRA administration panel, select versions and scroll mouse towards the end of the line for the particular version. From the dropdown list, select release and set the date).