raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11
pekko/scripts/release-train-issue-template.md
Seeta Ramayya ad0f3b4234
Replaced doc.akka.io with pekko.apache.org (#120) 
* modified all references in docs module

* replaced in inline scala docs

* renamed variable and changed access specifier

* reanmed in remaining places

* Adjusted path (instead of `akka` used `pekko`)

* Where applicable akka.io is replaced with pekko.apache.org

* replaced akka with pekko in the path

* Removed TODO

* Removed migration guide to gRPC (there is no user using pekko at the moment so no need of migration guide)

* Added back migration to gRPC section

* removed TODO

* alpakka is replaced with pekko-connectors

* the Akka online documentation -> the Pekko online documentation

* referring akka security docs

* reffering to akka migration guides (pekko is not managing them)

* Using pekkoBaseURL for platform-guide.base_url

* removed unnecessary redirects and used current instead of 2.6

* Changed akka discovery to pekko discovery

* Some more replacement

* fix merge issue

* revert platform-guide change because we

---------

Co-authored-by: PJ Fanning <pjfanning@users.noreply.github.com>
2023-01-31 12:26:50 +01:00

3.2 KiB
Raw Blame History

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: