pekko/scripts/release-train-issue-template.md
PJ Fanning 7e653454a9
use pekko: in urls and fix other branding issues (#184)
* use pekko: in urls and fix other branding issues

* update comments

* fix artery test

* test changes

* scalafmt

* try to fix some tests and fixing more akka refs

* more akka refs

* more changes

* more akka refs

* Update LeaseMajoritySpec.scala

* Update docs/src/main/paradox/testing.md

Co-authored-by: Johannes Rudolph <johannes.rudolph@gmail.com>

* Update docs/src/main/paradox/project/migration-guides.md

Co-authored-by: Johannes Rudolph <johannes.rudolph@gmail.com>

* Update actor/src/main/scala/org/apache/pekko/serialization/Serialization.scala

Co-authored-by: Johannes Rudolph <johannes.rudolph@gmail.com>

* Update scripts/release-train-issue-template.md

Co-authored-by: Johannes Rudolph <johannes.rudolph@gmail.com>

* revert link-validation change

* Update JacksonModule.scala

* revert key name changes to fix 2 tests

* fix one test

* more test trouble

* more test issues

* fix hashing test

* Update RouterTest.java

* update code comment

---------

Co-authored-by: Johannes Rudolph <johannes.rudolph@gmail.com>
2023-02-22 12:48:15 +01:00

3.2 KiB

Release Akka VERSION

Before the release

  • Make sure all important / big PRs have been merged by now
  • Create a news item draft PR on akka.io, using the milestone and scripts/authors.scala v2.6.14 v2.6.15
  • Make sure to update _config.yml in it
  • In case of a new minor release:
    • update the branch descriptions at CONTRIBUTING.md#branches-summary

Cutting the release

  • Make sure any running actions for the commit you would like to release have completed.
  • Tag the release git tag -a -s -m 'Release v$VERSION$' v$VERSION$ and push the tag git push --tags
  • Create a new milestone for the next version and close the current one.
  • Check that the GitHub Actions release build has executed successfully (it should publish artifacts to Sonatype and documentation to Gustav)
  • Update MiMa.latestPatchOf and PR that change (project/MiMa.scala)

Check availability

When everything is on maven central

  • ssh akkarepo@gustav.akka.io
    • update the current links on repo.akka.io to point to the latest version with
      ln -nsf $VERSION$ www/docs/akka/current
      ln -nsf $VERSION$ www/api/akka/current
      ln -nsf $VERSION$ www/japi/akka/current
      
    • check changes and commit the new version to the local git repository
      cd ~/www
      git add docs/akka/current docs/akka/$VERSION$
      git add api/akka/current api/akka/$VERSION$
      git add japi/akka/current japi/akka/$VERSION$
      git commit -m "Akka $VERSION$"
      
    • push changes to the remote git repository
      cd ~/www
      git push origin main
      

Announcements

  • Merge draft news item for akka.io
  • Create a GitHub release with the next tag version v$VERSION$, title and a link to the announcement
  • Post about it on the forum
  • Tweet using the @akkateam account (or ask someone to) about the new release
  • Announce on Gitter akka/akka
  • Announce internally

Update references

Update the versions used in:

These are autoupdated by latest stable on maven central: