Release Alpakka Kafka 2.0.5

[ennru]

~ 1 week before the release

• Check that any new deprecated annotations use the correct version name
• Check that open PRs and issues assigned to the milestone are reasonable
• Decide on a planned release date
• Notify depending projects (notably Lagom and Cloudflow) about the upcoming release
• Create a new milestone for the next version
• Check closed issues without a milestone and either assign them the 'upcoming' release milestone or invalid/not release-bound

1 day before the release

• Make sure all important / big PRs have been merged by now
• Check versions listed in home.md
• Communicate that a new version is about to be released in Gitter Akka Dev Channel, so that no new Pull Requests are merged

Preparing release notes in the documentation / announcement

• For non-patch releases: rename the 'akka-stream-kafka-x.x-stable' reporting project in WhiteSource accordingly (unfortunately this requires permissions that cannot be shared outside of Lightbend)
• Use the draft release notes to create/update the release notes in docs/src/main/paradox/release-notes/, listing contributors generated by sbt-authors (eg. sbt authors v1.1.0 HEAD)
• For non-patch releases: Create a news item draft PR on akka.github.com, using the milestone
• Move all unclosed issues for this milestone to the next milestone
• Release notes PR has been merged
• Close the 2.0.5 milestone

Cutting the release

• Wait until master build finished after merging the release notes
• Update the draft release with the next tag version v2.0.5, title and release description linking to the announcement, release notes and milestone
• Check that Travis CI release build has executed successfully (Travis will start a CI build for the new tag and publish artifacts to Bintray)
• Go to Bintray and select the just released version
• Go to the Maven Central tab and sync with Sonatype (using your Sonatype TOKEN key and password) (you may watch progress in the Staging repository)

Check availability

• Check API documentation
• Check reference documentation
• Check the release on Maven central

When everything is on maven central

• Log into gustav.akka.io as akkarepo
  • update the current links on repo.akka.io to point to the latest version with

    ln -nsf 2.0.5 www/docs/alpakka-kafka/current
    ln -nsf 2.0.5 www/api/alpakka-kafka/current
    ln -nsf 2.0.5 www/docs/alpakka-kafka/2.0
    ln -nsf 2.0.5 www/api/alpakka-kafka/2.0
    

  • check changes and commit the new version to the local git repository

    cd ~/www
    git add docs/alpakka-kafka/2.0 docs/alpakka-kafka/current docs/alpakka-kafka/2.0.5
    git add api/alpakka-kafka/2.0 api/alpakka-kafka/current api/alpakka-kafka/2.0.5
    git commit -m "Alpakka Kafka 2.0.5"
    

Announcements

• For non-patch releases: Merge draft news item for akka.io
• Send a release notification to Lightbend discuss
• Tweet using the akkateam account (or ask someone to) about the new release
• Announce on Gitter akka/alpakka-kafka
• Announce internally

Afterwards

• Update Alpakka Kafka dependency in Alpakka main repository
• Update version for Lightbend Supported Modules in private project
• Close this issue