You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure all important / big PRs have been merged by now
Communicate that a new version is about to be released in Gitter Akka Dev Channel, so that no new Pull Requests are merged
Preparing release notes in the documentation / announcement
For non-patch releases: rename the 'alpakka-x.x-stable' and 'alpakka-supported-x.x-stable' reporting projects in WhiteSource accordingly (unfortunately this requires permissions that cannot be shared outside of Lightbend)
Check readiness levels in /project/project-info.conf, and put in the release date for any new modules
Check supported projects listing in whitesourceSupported
Use the draft release notes to create/update the release notes in docs/src/main/paradox/release-notes/, listing contributors generated by sbt-authors (eg. authors v1.1.0 HEAD)
For non-patch releases: Create a news item draft PR on akka.github.com, using the milestone
Move all unclosed issues for this milestone to the next milestone
Fix up the draft release with the next tag version v2.0.0, title and release description linking to announcement, release notes and milestone
Check that Travis CI release build has executed successfully (Travis will start a CI build for the new tag and publish artifacts to Bintray and documentation to Gustav)
Go to Bintray and select the just released version
Go to the Maven Central tab, check the Close and release repository when done checkbox and sync with Sonatype (using your Sonatype TOKEN key and password)
~ 1 week before the release
deprecated
annotations use the correct version nameinvalid/not release-bound
1 day before the release
Preparing release notes in the documentation / announcement
/project/project-info.conf
, and put in the release date for any new moduleswhitesourceSupported
docs/src/main/paradox/release-notes/
, listing contributors generated bysbt-authors
(eg.authors v1.1.0 HEAD
)Cutting the release
v2.0.0
, title and release description linking to announcement, release notes and milestoneCheck availability
When everything is on maven central
gustav.akka.io
asakkarepo
current
links onrepo.akka.io
to point to the latest version withAnnouncements
Afterwards
The text was updated successfully, but these errors were encountered: