Release Akka HTTP 10.2.0

[jrudolph]

~ 1 week before the release

• [x] Check that open PRs and issues assigned to the milestone are reasonable
• [x] Triage tickets that should be ready for this release, add "pick next" label and release milestone
• [x] Triage open PRs and apply "pick next" label and maybe add to release milestone. Some PRs might be explicitly scheduled for this release, others might be ready enough to bring them over the finish line
• [x] Wind down PR queue. There has to be enough time after the last (non-trivial) PR is merged and the next phase. The core of the eco-system needs time to prepare for the final!
• [x] Decide on planned release date
• [x] Notify depending projects (notably Play + cinnamon) about upcoming release

1 day before the release

• [x] Make sure all important / big PRs have been merged by now
• [x] Check that latest nightly (once we have that) / master still works with depending projects (notably Play + cinnamon)
• [x] Communicate that a release 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

• [x] If this is a new minor (not patch) release, rename the 'akka-http-x.x-stable' reporting project in WhiteSource accordingly
• [x] Create a PR to add a release notes entry in docs/src/main/paradox/release-notes/. As a helper run scripts/commits-for-release-notes.sh <last-version-tag> which will output a list of commits grouped by submodule, and the closed issues for this milestone.
• [x] Create a PR on https://github.com/akka/akka.io with a news item draft -> https://github.com/akka/akka.io/pull/736/files
• [x] Create a PR on https://github.com/akka/akka.io updating Akka HTTP dependency for akka.io website: https://github.com/akka/akka.io/blob/master/_config.yml -> same PR
• [x] Release notes PR has been merged
• [x] Create a new milestone for the next version at https://github.com/akka/akka-http/milestones
• [x] Move all unclosed issues to the newly created milestone (or remove milestone) and close the version you're releasing

Cutting the release

• [x] Make sure there are no stray staging repos on sonatype
• [x] Wait until master build finished after merging the release notes
• [x] Create a tag for the release (e.g. v13.3.7) and push it. -> https://github.com/akka/akka-http/releases/tag/v10.2.0
• [x] Check that the Travis CI release build has executed successfully
• [x] Go to https://bintray.com/akka/maven/akka-http and select the just released version
• [x] Go to the Maven Central tab and sync with Sonatype. You may need to log in and switch to the 'Old Look' for this.
• [x] Log in to Sonatype to Close the staging repository (optional, should happen automatically if selected in Bintray)
• [x] Notify Telemetry / Play team to check against staged artifacts -> currently running
• [x] Run a test against the staging repository to make sure the release went well, for example by using https://github.com/akka/akka-http-quickstart-scala.g8 and adding the sonatype staging repo with resolvers += "Staging Repo" at "https://oss.sonatype.org/content/repositories/staging"
• [x] Release the staging repository to Maven Central.

Check availability

• [x] Check the release on maven central: https://repo1.maven.org/maven2/com/typesafe/akka/akka-http-core_2.13/10.2.0/

When everything is on maven central

• [x] Log into gustav.akka.io as akkarepo
  • [x] update the 10.1 and current links on repo.akka.io to point to the latest version with (replace the minor appropriately)

     ln -nsf 10.2.0 www/docs/akka-http/10.2
     ln -nsf 10.2.0 www/api/akka-http/10.2
     ln -nsf 10.2.0 www/japi/akka-http/10.2
     ln -nsf 10.2.0 www/docs/akka-http/current
     ln -nsf 10.2.0 www/api/akka-http/current
     ln -nsf 10.2.0 www/japi/akka-http/current

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

     cd ~/www
     git add docs/akka-http/ api/akka-http/ japi/akka-http/
     git commit -m "Akka HTTP 10.2.0"

• [x] Merge draft news item at https://github.com/akka/akka.io
• [x] Wait until the release page is published
• [x] Create the GitHub release with the tag, title and release description linking to announcement, release notes and milestone.

Announcements

• [x] Send a release notification to https://discuss.akka.io
• [x] Tweet using the akka account (or ask someone to) about the new release
• [x] Announce on Gitter at https://gitter.im/akka/akka

Afterwards

• [x] Merge https://github.com/akka/akka-http-quickstart-java.g8 update
• [x] Merge https://github.com/akka/akka-http-quickstart-scala.g8/pull/76 after validation
• [x] Make sure techhub guides / projects are actually updated -> triggered techhub rebuild
• [x] Add the released version to project/MiMa.scala to the mimaPreviousArtifacts key of all current compatible branches.
• [x] Forward port release notes from old releases to master
• [x] Update Akka HTTP reference in lightbend-platform-docs
• Close this issue

[jrudolph]

* Wait until [master build finished](https://travis-ci.org/akka/akka-http/builds/) after merging the release notes

Oops, now I know why... The master build already picked up the release tag and published the release at the same time as the release build... Removed the artifacts and restarted the release build.