Release Play 3.0.10/2.9.10

[mkurz]

Do the Release (Full document)

• Release projects that Play depends on
  Done already.

• Release Play itself

  • Look for PRs that should be merged.
  • Look at status:needs-backport, status:needs-forwardport issues/PRs (including closed ones).
  • Look at issues/PRs tagged milestone version (including closed ones).
  • Update any dependencies that are needed. (e.g JDK, Scala)
  • Make sure play uses new play-json, play-ws, twirl

• omnidoc

• Update play-samples

• Update playframework.com

  • Update .version in play-generated-docs
  • Update playReleases.json and changelog.md
  • Deploy the website changes
  • After documentation appeared online, restart the Algolia crawler

• Announce

  • Post on security mailing list if necessary
  • Publish a release at https://github.com/playframework/playframework/releases with a corresponding discussion
  • Tweet about the new release: https://twitter.com/playframework/
  • Announce in the Play LinkedIn group: https://www.linkedin.com/groups/3818467/
  • Announce in the Scala Enthusiasts LinkedIn group: https://www.linkedin.com/groups/746917/
  • Post an (email) update on the Play Open Collective page: https://opencollective.com/playframework#category-CONNECT
  • Post an (email) update in the GitHub Sponsors Dashboard https://github.com/sponsors/playframework/dashboard/updates (private link)
  • Post on Scala Reddit https://www.reddit.com/r/scala/
  • For Major releases, post to GitHub release radard: https://github.com/github/release-radar/issues/new?assignees=MishManners&labels=&template=release-radar-request.yml&title=%5BRelease+Radar+Request%5D+%3Ctitle%3E

• Post release tasks