Page History

...

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

...

Prerequisites

...

• 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:

  No Format
  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

• Make sure you are working with a clean repo (i.e. identical to upstream - no changes in progress). If needed clone a fresh copy
• git checkout trunk
• Check that current HEAD points to commit on which you want to base new  release branch. Checkout particular commit if not.
• git branch 0.10.0
• git push apache 0.10.0
• Check that the branch was correctly propagated to Apache using the webui: https://git-wip-us.apache.org/repos/asf?p=kafka.git
• Modify the version in 0.10.0 branch to remove "-SNAPSHOT" in gradle.properties, tests/kafkatest/__init__.py and kafka-merge-pr.py. Commit and push to 0.10.0 branch in apache.
• Modify the version in trunk to bump to the next one "0.10.1.0-SNAPSHOT" in gradle.properties, tests/kafkatest/__init__.py and kafka-merge-pr.py. Commit and push to trunk in apache.

• Send email announcing the new branch:

  No Format

  To: dev@kafka.apache.org Subject: New release branch 0.10.0 Hello Kafka developers and friends, As promised, we now have a release branch for 0.10.0 release (with 0.10.0.0 as the version). Trunk has been bumped to 0.10.1.0-SNAPSHOT. I'll be going over the JIRAs to move every non-blocker from this release to the next release. From this point, most changes should go to trunk. *Blockers (existing and new that we discover while testing the release) will be double-committed. *Please discuss with your reviewer whether your PR should go to trunk or to trunk+release so they can merge accordingly. *Please help us test the release! * Thanks! $RM

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

...