Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.12.11 #664

SethTisue opened this issue Jan 31, 2020 · 0 comments

Release 2.12.11 #664

SethTisue opened this issue Jan 31, 2020 · 0 comments


Copy link

@SethTisue SethTisue commented Jan 31, 2020

Release lead: @lrytz

Variables to be expanded in this template (or export them in a local terminal, so that you can copy/paste the commands below without replacing anything):

  • SCALA_VER_BASE="2.12.11"
  • SCALA_SHA=????????????????????????????????????????
  • DIST_SHA=????????????????????????????????????????

Key links:

N weeks before the release

  • Wind down PR queue. There has to be enough time after the last (non-trivial) PR is merged and the next phase. The core of the eco-system needs time to prepare for the final!
  • Triage scala/bug and scala/scala-dev tickets
  • Create next scala/scala milestone, move the magical "Merge to 2.13.x" description to it (so Scabot uses it as default for new PRs)
  • Close the scala/bug milestone, create next milestone, move pending issues
  • Close the scala/scala-dev milestone, create next milestone, move pending issues
  • Check PRs assigned to the milestone, also check WIP
  • Announce expected release date and current nightly "release candidate" (nightly sha-mangled version) at on

Release announcement / notes

  • Notify community on
  • Review merged PRs, make sure release-notes label is applied appropriately
  • PRs with release-notes label must have excellent title & description (title will be pasted literally in release note bullet list)
  • Draft release notes (to be published once GitHub tag is pushed)
    • note that GitHub release notes drafts can only be viewed by committers, so use a gist to draft the notes, so the gist can be shared with the community
  • On contributors thread, link to release note gist and request feedback

N days before release

  • Announce no more PRs will be merged unless last-minute regressions are found. Re-iterate current nightly sha version for testing.
  • Community build
  • Run scala-collections-laws and evaluate results
    • Rex Kerr (@Ichoran) is the keeper and expert on this
  • Windows Jenkins job
  • Check any merged PRs accidentally assigned to the next milestone in this branch, and re-assign them to this milestone
  • Merge in any older release branch
  • Check module versioning (is everything in up to date?)
  • On major release, bump PickleFormat version

Point of no return

Check availability

When everything is on maven central


  • if it's a 2.12.x release, publish macro paradise for the new version



Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.