Page History

...

• Go to https://repository.apache.org/#stagingRepositories, find the uploaded artifacts and drop it.
• Go back to the beginning  - don't forget to bump the RC number.

 After the vote passes

• Remember: at least 3 days, 3 +1 from PMC members (committers are not enough!) and no -1.
• Merge the last version change / rc tag into the release branch
• Create a new tag for the release, on the same commit as the voted rc tag:
  • Use "git show 0.10.0.0-rc6" to find the commit hash of the tag
  • git tag -a 0.10.0.0 <commit hash>
• Update version on the branch to 0.10.0.1

• Send a vote closing email:

  No Format

  To: dev@kafka.apache.org Subject: [RESULTS] [VOTE] Release Kafka version 0.10.0.0 This vote passes with 8 +1 votes (4 bindings) and no 0 or -1 votes. +1 votes PMC Members: * $Name * $Name To: dev@kafka.apache.org Subject: [RESULTS] [VOTE] Release Kafka version 0.10.0.0 This vote passes with 7 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * $Name * $Name * $Name Committers: * $Name * $Name Community: * $Name * $Name 0 votes * No votes -1 votes * No votes Vote thread: http://markmail.org/message/faioizetvcils2zo I'll continue in the release process and announce a release in the next few days. $RM

• Close JIRA version
• Upload all artifacts, release notes, and docs to https://dist.apache.org/repos/dist/release/kafka (a SVN repo, using Apache committer id/passwd)
  • svn co https://dist.apache.org/repos/dist/release/kafka kafka-release
  • create a new directory for the release (for example kafka-release/0.10.0.0)
  • copy the release artifacts from the latest RC (the ones who were in your people.apache.org directory) to the new release directory
  • Add the directory to SVN: svn add 0.10.0.0

  • # Optionally change KEYS file in case that you've added your key for the first time

  • svn commit -m "Release 0.10.0.0"

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

...