Release 2.12.3

[retronym]

Milestone: https://github.com/scala/scala/milestone/61

Target date: July 17

Before the release

• Notify community on https://contributors.scala-lang.org/c/announcements
• Create next milestone, move the "Merge to 2.13.x" description to it (default for new PRs)
• Close the milestone
• Triage scala/bug and scala/scala-dev tickets that target [version]
• Check PRs assigned to the milestone, also check WIP
• Check merged PRs for the next milestone in this branch, and assign them to this milestone.
• Check module versioning
• Merge in older release branch

Release notes

• 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)
  • https://github.com/scala/scala/releases/edit/v[version]
• Summarize release notes and submit to https://github.com/typesafehub/techhub-blog => https://github.com/typesafehub/techhub-blog/pull/19
• Prepare PR to https://github.com/scala/scala-lang/ (using scala/make-release-notes)
  • documentation/api.md
  • download/index.md
  • _config.yml (update devscalaversion or scalaversion)
  • => Announce Scala 2.12.3 scala-lang#713

Actual release

• Announce start of release process, point to release note PRs for feedback
• Close the scala/bug milestone, create next, move pending issues
• Close the scala-dev milestone, create next, move pending issues
• Double check version.properties, maybe create a PR with updates

Stage the release

• Run the build job, specify SCALA_VER_BASE and SCALA_VER_SUFFIX: scala-2.12.x-release-main#878
  • Note the scala/scala@NNNNNN commit built by integrate-bootstrap job (on jenkins page): 6ac6da8b61a3a427089a166c7802a940eac71064
  • Create tag locally: git tag -s -m "Scala [version]" v[version] [sha],
  • Note the scala/scala-dist@NNNNNN commit built by package-unix job (on jenkins page): e49f4b3a8b9d83d21f7c50e283f5426808f21231
  • Create tag locally: git tag -s -m "Scala [version]" v[version] [sha],
  • Staging repo to be promoted after tag is cut (see log of the boostrap job): orgscala-lang-1432
• Sanity check jar/pom in https://oss.sonatype.org/content/repositories/staging/org/scala-lang/scala-compiler/2.N.M/ (and a module)
• Announce release is staged at https://oss.sonatype.org/content/repositories/staging/ on https://contributors.scala-lang.org/c/announcements

Point of no return

• Push scala/scala tag: git push https://github.com/scala/scala.git v[version]
• Before the next nightly, advance HEAD on scala/scala past the tag. Otherwise, the nightly build will re-stage the release and overwrite the distribution archives on S3. TODO: should we disable this? Tag driven distribution publication was disabled in Disable tag driven publication of distribution scala#5979
• Push scala/scala-dist tag: git push https://github.com/scala/scala-dist.git v[version]
• Promote staging repos: st_stagingRepoPromote [scala-repo], st_stagingRepoPromote [modules-repo]

Check availability

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

When everything is on maven central

• Create PR to update versions.properties (new file generated by the bootstrap job) and the baseVersion in build.sbt
• Pre-announce the release on https://contributors.scala-lang.org/c/announcements
• Check that the API docs are published
  • http://www.scala-lang.org/api/[version]/
• 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

Announcements

• Scala Users discourse https://users.scala-lang.org
• Tweet from @scala_lang

[retronym]

Pre-announce draft:

2.12.3

• Release Checklist
• Change log: Full / Curated
• Expected release date: July 17

Highlights:

• Compiler performance has been improved significantly (related changes
• A new optimizer setting -opt-inline-from limits the classes from which the inliner will copy code. scalac -opt-inline-from:help provides detailed help.
• The presentation compiler has improved support for implicit macros, which should improve the experience with libraries based on Shapeless. It also has better support for code completion for dependently typed methods.

2.13.0-M2

• 2.13.0-M2
• Change log: Full / Curated
• Expected release date: Late July

The REPL is undergoing renovations and features better positioning of errors and a cleaner internal implementation. multi-line editing and syntax highlighting.

Right associative methods with a by-name parameter no longer eagerly evaluate the operand.

Furthermore, all changes in the 2.12.3 will be part of 2.13.0-M2.

What's next?

We are planning to make 2.13.x the default branch for pull requests after these releases to help us focus our collective attention on working towards 2.13.0. We'll still target some changes to 2.12.x that are high reward and low risk, that fix important regressions.

[xeno-by]

Compiler performance has been improved significantly

Omg hype!! Can't wait for the release date. 💖

[som-snytt]

call me hyped. My favorite part is "point of no return". Do I need a bungie cord?

[retronym]

"point of no return" sounds like the next SIP-18 language flag.

[retronym]

The release build for 2.12.3 failed with:

[info] :: delivering :: org.scala-lang#junit;2.12.3 :: 2.12.3 :: release :: Mon Jul 24 08:37:49 UTC 2017
[info] 	delivering ivy file to /home/jenkins/workspace/scala-2.12.x-integrate-bootstrap/target/junit/ivy-2.12.3.xml
java.io.IOException: PUT operation to URL https://oss.sonatype.org/service/local/staging/deploy/maven2/org/scala-lang/scala-library-all/2.12.3/scala-library-all-2.12.3.pom failed with status code 504: GATEWAY_TIMEOUT
	at org.apache.ivy.util.url.AbstractURLHandler.validatePutStatusCode(AbstractURLHandler.java:82)
	at org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:264)
	at org.apache.ivy.util.FileUtil.copy(FileUtil.java:150)
	at org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:84)

In any case, we had one extra PR to add to the release, scala/scala#6004, so we'll need to re-run anyway.

However, the subsequent nightly build failed with: #409 which I'll have to look at first.

Optimistically kicking off the release build while I investigate: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-release-main/876/console

[retronym]

#409 is a latent bug, let the release roll on.

[lrytz]

#409 hit again on the next attempt (https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-bootstrap/1042/consoleFull)

[info] ! type deconstruction.tuple type (3): Exception raised on property evaluation.
[info] > Exception: java.lang.IllegalArgumentException: requirement failed: Tuples with 3 arity aren't supported

Starting another one... https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-release-main/878/

[retronym]

Might be prudent to add a workaround for #409, maybe something changed to make the race condition more likely to trip?

[lrytz]

Yeah - at least the build passed now. https://scala-ci.typesafe.com/job/scala-2.12.x-release-main/878/ I'll announce the staging tomorrow (if nobody does it before).

[retronym]

I've announced the staged release.

[jvican]

I have just compiled Zinc with 2.12.3. Everything's good on my end.

[xeno-by]

https://oss.sonatype.org/content/repositories/releases/org/scalamacros/paradise_2.12.3/2.1.0/

[xeno-by]

For those who'll want to try out the 2.12.3 prerelease, here are the required changes to your sbt builds: https://github.com/scalamacros/paradise/blob/2c7f071ecd1d0e75b678fbdc81fc0e6e80042edf/project/build.scala#L6-L7.

[DavidGregory084]

resolvers += Resolver.sonatypeRepo("staging") also works