alpakka
alpakka copied to clipboard
Release 7.0.2
Release Alpakka 7.0.2
Cutting the release
- [x] Check that open PRs and issues assigned to the milestone are reasonable
- [x] Update the Change date and version in the LICENSE file.
- [x] Check readiness levels in
/project/project-info.conf
, and put in the release date for any new modules. - [x] Create a new milestone for the next version
- [x] Close the 7.0.2 milestone
- [x] Make sure all important PRs have been merged
- [ ] Update the revision in Fossa in the Akka Group for the Akka umbrella version, e.g.
22.10
. Note that the revisions for the release is udpated by Akka Group > Projects > Edit. For recent dependency updates the Fossa validation can be triggered from the GitHub actions "Dependency License Scanning". - [x] Wait until main build finished after merging the latest PR
- [x] Update the draft release with the next tag version
v7.0.2
, title and release description. Use thePublish release
button, which will create the tag. - [x] Check that GitHub Actions release build has executed successfully (GitHub Actions will start a CI build for the new tag and publish artifacts to https://repo.akka.io/maven)
Check availability
- [x] Check API documentation
- [x] Check reference documentation. Check that the reference docs were deployed and show a version warning (see section below on how to fix the version warning).
- [x] Check the release on https://repo.akka.io/maven/com/lightbend/akka/akka-stream-alpakka-xml_2.13/7.0.2/akka-stream-alpakka-xml_2.13-7.0.2.pom
When everything is on https://repo.akka.io/maven
- [x] Log into
gustav.akka.io
asakkarepo
- [x] If this updates the
current
version, run./update-alpakka-current-version.sh 7.0.2
- [x] otherwise check changes and commit the new version to the local git repository
cd ~/www git status git add docs/alpakka/current docs/alpakka/7.0.2 git add api/alpakka/current api/alpakka/7.0.2 git commit -m "Alpakka 7.0.2"
- [x] If this updates the
Announcements
For important patch releases, and only if critical issues have been fixed:
- [ ] Send a release notification to Lightbend discuss
- [ ] Tweet using the @akkateam account (or ask someone to) about the new release
- [ ] Announce on Gitter akka/akka
- [ ] Announce internally (with links to Tweet, discuss)
For minor or major releases:
- [ ] Include noteworthy features and improvements in Akka umbrella release announcement at akka.io. Coordinate with PM and marketing.
Afterwards
- [ ] If Cassandra has relevant changes, create/update PR in Akka Persistence Cassandra to upgrade to 7.0.2
- [ ] Update akka-dependencies bom
- [x] Create an issue or PR to upgrade projects in Alpakka Samples
- Close this issue