Page History

...

Go to JIRA, move all unresolved jiras with "Fix versions" of 0.910.0.0 to future releases.
Select roadmap from left panel, click on "release notes" next to the release version and prepare/format the html release notes. The html version shows up at the bottom of the page. Save the release notes as RELEAERELEASE_NOTES.html
Upload the release notes to home.apache.org

...

sign the artifacts:

for file in *.tgz; do gpg --armor --output $file.asc --detach-sig $file; done

for file in *.tgz; do gpg --verify $file.asc $file; done

for file in *.tgz; do gpg --print-md md5 $file > $file.md5; done

for file in *.tgz; do gpg --print-md sha1 $file > $file.sha1; done

for file in *.tgz; do gpg --print-md sha512 $file > $file.sha2; done

Prepare java and scala docsthe aggregated javadoc.

Upload all the binary artifacts, release notes, java and scala doc to your home.apache.org URL.

...

Make sure the documentation (docs/documentation.html, docs/quickstart.html,docs/api.html) are all referring to the correct release and links.
Git clone https://git-wip-us.apache.org/repos/asf/kafka-site.git
checkout Checkout the branch asf-site
The releaseTarGzAll target should auto-generate the configuration docs for broker/producer/consumer in ./core/build/distributions/kafka_2.1011-0.910.0.0-site-docs.tgz. Untar the file in 090/and rename site-docs to 0100 (or if the latter already exists, replace its contents).
Copy release javadoc to newly 090to 0100/.
Update documentation.html to include the new documentation link (0900100/documentation.html).
Update protocol.html to include the new protocol guide link (0900100/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).

...

Space shortcuts