Release 2.12.10

[SethTisue]

release lead: @SethTisue

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.10"
• SCALA_VER_SUFFIX=""
• SCALA_SHA=61701c22900f14676fa181500722b64330eb2605
• DIST_SHA=b0a041bd1b13397dfb56d7b61224ffc5472c9056
• SCALA_VER="$SCALA_VER_BASE$SCALA_VER_SUFFIX"

Key links:

• scala/scala milestone: https://github.com/scala/scala/milestone/82
• scala/bug milestone: https://github.com/scala/bug/milestone/102
• scala/scala-dev milestone: https://github.com/scala/scala-dev/milestone/29

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 https://scala-ci.typesafe.com/artifactory/scala-integration/ on https://contributors.scala-lang.org/c/announcements

Release announcement / notes

• Notify community on https://contributors.scala-lang.org/c/announcements
  • https://contributors.scala-lang.org/t/scala-2-12-10-release/3658
• 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
  • https://gist.github.com/SethTisue/3ed4ff57d40c744cbf4238eb21f2cfad
• 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
  • won't be anywhere near all green, but we should make sure some nontrivial number of projects are still green
  • run with expected-greens only: https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-community-build/?
  • also do a full run to see if there are any unexpected greens
• Run scala-collections-laws and evaluate results
  • Rex Kerr (@Ichoran) is the keeper and expert on this
• Windows Jenkins job
  • don't just trust the automated nightly runs, manually trigger a run on the exact SHA
  • https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-windows/1487/
• 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 versions.properties up to date?)
• On major release, bump PickleFormat version

Point of no return

• Once sufficient time has passed since last merged PR (1-2 weeks depending on whether it's a maintenance or development branch), and core projects have tried out the candidate nightly, it's time to cut the release!
• Make sure there are no stray staging repos on sonatype
• Trigger a build on travis, specify SCALA_VER_BASE and SCALA_VER_SUFFIX in the custom config
  • config: before_script: export SCALA_VER_BASE=$SCALA_VER_BASE SCALA_VER_SUFFIX=$SCALA_VER_SUFFIX)
  • https://travis-ci.org/scala/scala/builds/583358653
  • Check the build status on https://github.com/scala/scala/commits/2.12.x
  • Check that the scala/scala job also triggered a following scala/scala-dist job
    • https://travis-ci.org/scala/scala-dist/builds/583371597
  • Note the scala/scala commit (the full 40-char sha!)
    • 61701c22900f14676fa181500722b64330eb2605
  • Create the scala/scala tag locally: git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $SCALA_SHA
  • Note the scala/scala-dist commit (the full 40-char sha!)
  • Create scala-dist tag locally: git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $DIST_SHA
  • Note the repos to be promoted after tag is cut (see travis log)
    • https://oss.sonatype.org/content/repositories/orgscala-lang-1845
    • https://oss.sonatype.org/content/repositories/orgscala-lang-1846
    • https://oss.sonatype.org/content/repositories/orgscala-lang-1847
• Sanity check jar/pom
  • https://oss.sonatype.org/content/repositories/staging/org/scala-lang/scala-compiler/$SCALA_VER/
  • in particular, if the release was staged multiple times, double check that https://oss.sonatype.org/content/repositories/staging/ has the files from the most recent build
• Check that JARs haven't mysteriously bloated — compare sizes to previous release. We have no other backstop for this.
• Remember, tags are forever, so are maven artifacts (even staged ones, as they could end up in local caches) and S3 uploads (S3 buckets can be changed, but it can takes days to become consistent)
• Push scala/scala tag: git push https://github.com/scala/scala.git v$SCALA_VER
• Add release notes to https://github.com/scala/scala/releases/tag/v$SCALA_VER
• Push scala/scala-dist tag: git push https://github.com/scala/scala-dist.git v$SCALA_VER
• Trigger two scala-dist jobs on travis (https://travis-ci.org/scala/scala-dist) with custom config. must use full-length SHAs!
  • before_script: export version=$SCALA_VER scala_sha=$SCALA_SHA mode=archives: https://travis-ci.org/scala/scala-dist/builds/583434523
  • before_script: export version=$SCALA_VER scala_sha=$SCALA_SHA mode=update-api: https://travis-ci.org/scala/scala-dist/builds/583434607
• Promote staging repos: st_stagingRepoPromote [scala-repo], st_stagingRepoPromote [modules-repo] (or use oss.sonatype.org web UI)

Check availability

• Check release on sonatype: https://oss.sonatype.org/content/repositories/releases/org/scala-lang/scala-compiler/2.12.10/
• Check the release on maven central: http://central.maven.org/maven2/org/scala-lang/scala-compiler/2.12.10/
• Check the release on maven search (takes longer): http://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.scala-lang%20v%3A2.12.10

When everything is on maven central

• Prepare PR to https://github.com/scala/scala-lang/ (using scala/make-release-notes which requires a staged release and a pushed tag)
  • documentation/api.md
  • download/index.md
  • _config.yml (update devscalaversion or scalaversion)
• Prepare PR to https://github.com/scala/docs.scala-lang/
  • api/all.md
• make sure the draft release notes are on GitHub tag: https://github.com/scala/scala/releases/tag/v$SCALA_VER
• Pre-announce the release on https://contributors.scala-lang.org/c/announcements
• On 2.13.0 only: (manually) update the current symlink for the API docs
  • https://github.com/scala/scala-dist/blob/2.13.x/scripts/jobs/release/website/update-api#L15
• Check that the API docs are published
  • http://www.scala-lang.org/api/$SCALA_VER/
  • https://docs.scala-lang.org/api/all.html ?
• Merge the scala-lang PR and the docs.scala-lang.org PR
  • wait for them to arrive on the websites and make sure they look okay

Modules

• build and release scala-collection-compat and other modules (or open tickets asking that the maintainers do so)
  • this work has moved to https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md
• if it's a 2.12.x release, publish macro paradise for the new version

Announcements

• Scala Users discourse https://users.scala-lang.org
• add a reply on the same https://contributors.scala-lang.org thread where you announced that the release process was starting
• Tweet from @scala_lang
• https://gitter.im/scala/scala
  • if you feel like it, say something in https://gitter.im/scala/contributors too
• ask Seth to announce on #scala IRC

Afterwards

• Create PR to add/update spec links on scala-lang.org (example: update spec links and advisements scala-lang#1050)
• Create PR to update scala-version on docs.scala-lang.org (example: bump scala-version docs.scala-lang#1294)
• Create PR to update versions.properties (new file generated by the bootstrap job) and the baseVersion in build.sbt and the MiMa base version and exclusion filters and (if it's a major bump) spec/_config.yml
• If it's a major bump:
  • PR an update to latestSpecVersion in spec/_config.yml on the old branch, so that spec is marked as no longer current
  • Ditto for the nightly build and spec links in _data/footer.yml and _data/doc-nav-header.yml on docs.scala-lang.org
• Create PR to update https://github.com/lightbend/reactive-platform-docs/blob/master/src/main/paradox/supported-modules/index.md
• Update WhiteSource

[SethTisue]

the original scala-dist job https://travis-ci.org/scala/scala-dist/builds/583371597 failed with

[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::              FAILED DOWNLOADS            ::
[warn] 	:: ^ see resolution messages for details  ^ ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.scala-lang#scala-library;2.10.7!scala-library.jar
[warn] 	:: org.scala-lang#scala-compiler;2.10.7!scala-compiler.jar
[warn] 	:: org.scala-lang#scala-reflect;2.10.7!scala-reflect.jar
[warn] 	:: org.scala-lang#jline;2.10.7!jline.jar
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::

no real clue why, but decided to bump scala-dist version from sbt 0.13.17 to 0.13.18 to see if that would help: scala/scala-dist#208

triggered new scala-dist job: https://travis-ci.org/scala/scala-dist/builds/583399629 and it got farther this time

[error] download failed: org.scala-lang#scala-compiler;2.12.10!scala-compiler.jar
[error] unresolved dependency: org.scala-lang#scala-dist;2.12.10: not found

I think this means the Scala JARs have to hit Maven Central first? so I released the staging repos, now waiting for Maven Central sync. watching https://repo1.maven.org/maven2/org/scala-lang/scala-library/2.12.10/

[SethTisue]

JARs are on Maven Central, but when I re-ran https://travis-ci.org/scala/scala-dist/builds/583399629 it hit the 2.10.7 JAR error again, so apparently the 0.13.18 upgrade didn't fix anything, apparently I just need to hit "restart" until it works? :-/

[SethTisue]

I tried removing sonatype-staging from conf/repositories on a wip branch in the scala-dist repo and triggering a build with that: https://travis-ci.org/scala/scala-dist/builds/583412119

I guess the purpose of having sonatype-staging in there is so you can run the scala-dist job even before the Scala JARs have gone to Maven Central, but apparently sonatype-staging isn't operating reliably today; that would account for both kinds of errors I ran into (the missing 2.10.7 JARs and the missing 2.12.10 JARs)

but I don't understand why failures to resolve 2.0.7 from sonatype-staging would matter, why wouldn't it just use maven central instead, conf/repositories has maven central

but anyway the conf/repositories change seems to be working, the job seems to be succeeding. (but it's dinnertime.)

[SethTisue]

job succeeded https://travis-ci.org/scala/scala-dist/builds/583412119

in the scala-dist repo, I attached the v2.12.10 tag to the HEAD of 2.12.x rather than to the commit in my branch, since the branch was merely working around an issue we hope/believe was merely transient

[SethTisue]

https://travis-ci.org/scala/scala-dist-smoketest/builds/583436738 passed (though I had to manually trigger it, it didn't automatically run for some reason)

but both the archives and update-api jobs failed, I don't know why, I'll have to look at it tomorrow:

• https://travis-ci.org/scala/scala-dist/builds/583434523
• https://travis-ci.org/scala/scala-dist/builds/583434607

[SethTisue]

but both the archives and update-api jobs failed, I don't know why,

it seems that the other dists uploaded successfully but the .msi did not

[SethTisue]

I'm out of time. I can pick this back up tomorrow, unless another team member gets to it first? once the .msi is in place, then the archives and update-api jobs should be restarted and the website PRs should be merged

[lrytz]

Since I could download the msi on my machine, I just tried re-running the jobs, and they went green. Glitch in the Matrix I guess.

[plokhotnyuk]

@SethTisue please use the AND operator in the request to the Maven Search: https://search.maven.org/search?q=g:org.scala-lang%20AND%20v:2.12.10

[SethTisue]

@plokhotnyuk nice catch, thanks for spotting that! fixed

[SethTisue]

paradise publishing remains, closing anyway since there's a ticket now: scalamacros/paradise#121