Closed raboof closed 4 years ago
* 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-M1 www/docs/akka-http/10.1 ln -nsf 10.2.0-M1 www/api/akka-http/10.1 ln -nsf 10.2.0-M1 www/japi/akka-http/10.1 ln -nsf 10.2.0-M1 www/docs/akka-http/current ln -nsf 10.2.0-M1 www/api/akka-http/current ln -nsf 10.2.0-M1 www/japi/akka-http/current ```
Apart from that being a bit wrong about the minor version, I think we shouldn't yet update the current
link yet.
~ 1 week before the release
1 day before the release
Preparing release notes in the documentation / announcement
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.scripts/authors.scala previousVersion master
Cutting the release
v13.3.7
), title and release description linking to announcement, release notes and milestone.resolvers += "Staging Repo" at "https://oss.sonatype.org/content/repositories/comtypesafe-xxx"
sbt -Dakka.genjavadoc.enabled=true ++2.12.9 "deployRsync akkarepo@gustav.akka.io"
to deploy API and reference documentation.Check availability
When everything is on maven central
gustav.akka.io
asakkarepo
10.1
andcurrent
links onrepo.akka.io
to point to the latest version with (replace the minor appropriately)Announcements
Afterwards
project/MiMa.scala
to themimaPreviousArtifacts
key of all current compatible branches.