Page History

...

We should improve the release script to include these steps. In the meantime, for new releases:

• Make sure the docs/documentation.html is referring to the correct release and links.
• git clone https://git-wip-us.apache.org/repos/asf/kafka-site.git
• git checkout asf-site
• Update the website content including docs:
  • The gradle target releaseTarGz auto-generates
  The releaseTarGzAll target should auto-generate
  • the configuration docs for broker/producer/consumer
  in 
  • /etc in ./core/build/distributions/kafka_2.
  11
  • 13-
  0
  • 2.
  10
  • 8.0
  .0
  • -site-docs.tgz.
  • Untar the file and rename the site-docs/ folder to
  0100
  • 28/ (or, if the latter already exists, replace its contents).
• Update the javadocs:
  Copy release javadoc to 0100 (
  • Create the release Javadocs with the gradle target aggregatedJavadoc, with output under ./build/docs/javadoc/.
  • Copy the javadoc folder to 28/ (i.e., the full path is 28/javadoc/). If this is bug fix release, do this after the vote has passed to avoid showing an unreleased version number in the published javadocs
  )
  • .
  Javadocs can be generated with the aggregatedJavadoc Gradle target
  • Commit

  Blog Post

  • For major releases, consider writing a blog in https://blogs.apache.org/kafka/. If you don't have a blog account, just log into blogs.apache.org once with your Apache credential and notify the Kafka PMC chair, who can then invite you to the blog space. Follow the instructions for creating a preview.  Send the a link to the preview blog post to dev mailing for comments before publishing. (See INFRA-20646 for an issue about previews of blog entry drafts.)
  • Consider incorporating any suggestions from the dev thread until release is annou

  ...