Release 2.13.0-M1

[adriaanm]

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

Target date: April 1, 2017

Before the release

• Notify community on https://contributors.scala-lang.org/c/announcements
  • https://contributors.scala-lang.org/t/upcoming-scala-releases-2-11-9-2-12-2-and-2-13-0-m1/599
• Create next milestone, move the "Merge to 2.13.x" description to it (default for new PRs)
• Close the milestone
• Check the osgi test logs: check osgi test log in 2.13 boostrap #351
• Start drafting release notes
• Triage scala/bug and scala-dev tickets that target [version]
• Check PRs assigned to the milestone, also check WIP

Prepare for first milestone

• Add parallel collections to community build (add parallel collections module to 2.13 build and fix key projects to use it community-build#495)
• Check module versioning, currently hard-coded to 2.12
  • https://github.com/scala/scala/blob/2.13.x/project/VersionUtil.scala#L166-L169
  • scala/scala@5e62f13#diff-19e53133756351b63e653b6a14dfc5ccL139
  • Done: Set scala.binary.version to 2.12 until 2.13.0-M1 is out scala#5810
• Merge 2.12.x to 2.13.x

Actual release

• Announce start of release process
• Close the scala/bug milestone, create next, move pending issues
  • https://github.com/scala/bug/milestone/8
• Close the scala-dev milestone, create next, move pending issues
  • https://github.com/scala/scala-dev/milestone/13
• Double check version.properties, maybe create a PR with updates
• Note the scala/scala commit sha
  • scala/scala@97319fb
• Note the scala/scala-dist commit sha
  • scala/scala-dist@0025005

Run the build

• Run the build job, specify SCALA_VER_BASE and SCALA_VER_SUFFIX
  • https://scala-ci.typesafe.com/job/scala-2.13.x-release-main/178/
• Staging repo (see log of the boostrap job)
  • https://oss.sonatype.org/content/repositories/orgscala-lang-1404/
• In each staging repo, sanity-check a JAR (check library.properties in scala-library.jar)
• In each staging repo, sanity-check a POM (scala-xml)
• Announce the staging repos on https://contributors.scala-lang.org/c/announcements
  • https://contributors.scala-lang.org/t/upcoming-scala-releases-2-11-11-2-12-2-and-2-13-0-m1/599/10

Point of no return

• Tag scala/scala: git tag -s -m "Scala [version]" v[version] [sha], git push https://github.com/scala/scala.git v[version]
• Tag scala/scala-dist: git tag -s -m "Scala [version]" v[version] [sha], 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
  • Note: this is important to move the branch ahead of the tag. Otherwise the nightly build will re-stage the release and overwrite the distribution archives on S3.
  • Bump version numbers after 2.13.0-M1 scala#5858
• 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

Release notes

• Add the release notes to the GitHub tag
  • https://github.com/scala/scala/releases/edit/v[version]
• Create PR to https://github.com/scala/make-release-notes, only include a short summary of the release notes
• Prepare PR to https://github.com/scala/scala-lang/
  • documentation/api.md
  • download/index.md
  • _config.yml (update devscalaversion or scalaversion)

Announcements

• Scala Users discourse https://users.scala-lang.org
  • https://users.scala-lang.org/t/scala-2-11-11-2-12-2-and-2-13-0-m1-are-released/377
• Tweet from @scala_lang
  • https://twitter.com/adriaanm/status/854378932526764033

Release modules

For binary incompatible releases, release modules that are not built during the scala/scala bootstrap (or ask maintainrs to do so)

• https://github.com/rickynils/scalacheck
• https://github.com/scala/scala-xml: built during the bootstrap
• https://github.com/scala/scala-partest: built during the bootstrap
• https://github.com/scala/scala-parallel-collections
• https://github.com/scala/scala-parser-combinators
• https://github.com/scala/scala-swing
• https://github.com/scala/scala-continuations
• https://github.com/scala/scala-java8-compat
• https://github.com/scala/async
• https://github.com/scala/pickling: not critical, sbt 0.x stays is on Scala 2.10, and sbt 1.x won't depend on it.

Once scalacheck is available

• Update the hard-coded 2.12 binary version in the scalacheck dependency to [version]
  • Hard-coding the binary version there (instead of using scala.binary.version in versions.properties) allows bumping versions.properties right after a release, without waiting for scalacheck.
  • We can hopefully keep using a fixed binary version during the entire milestone / RC cycle and avoid in-sourcing scalacheck, like we do for our modules. In any case, we only depend on it internally for running the tests.
  • https://github.com/scala/scala/blob/v2.13.0-M1/build.sbt#L45
  • Done: Use 2.13 binary version for scalacheck scala#5860

[SethTisue]

as of just now, the 2.13 community build is green again. (in some cases I have actually fixed failures, other times I have just disabled something partially or completely. whatever enables getting to green without spending too much time on it, this early in the game.)

[adriaanm]

Excellent!

[SethTisue]

after some further fixes (specs2, scala-js) and removals, 2.13 community build is green again: scala/community-build#508

[lrytz]

Thank you, Seth!

[SethTisue]

@lrytz after the 2.12->2.13 merge, bootstrap failed because of fatal warnings in scala-partest. I don't have time to look into it (I need to prioritize 2.12 stuff), but https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-bootstrap/325/artifact/logs/builds/*view*/ shows the error. the needed fix was already merged at scala/scala-partest#83, but I guess the scala repo is still using whatever was tagged as 1.1.0? (just guessing, I haven't looked at the module bootstrap stuff in a while)

[lrytz]

M1 is staged at https://oss.sonatype.org/content/repositories/orgscala-lang-1404/

[milessabin]

I'm somewhat concerned that you must have completely disabled the community build for Scala.js. Scala.js isn't available for 2.13.x yet, with the upshot that basically none of the ecosystem can be released for 2.13.0-M1, and my worry is that the community build being green is giving a false sense of security.

For previous milestones you did a great job of assembling a list of community projects which supported the milestone ... I think it would be a good idea if you could do that again before advertising 2.13.0-M1 more widely.

[lrytz]

you must have completely disabled the community build for Scala.js

Scala.js was successfully built during the release testing (which runs the community build) https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-community-build/345/console.

I guess you know, but just to make sure, we have the list of community projects for 2.13: https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md

I think you're right that for 2.12 milestones / RCs, we typically had a substantial part of the eco-system available before announcing. We should try to make that happen for 2.13 too.

In any case, M1 is all about sorting out this kind of release boostrap questions.

[sjrd]

There's no release of Scala.js for 2.13.0-M1 yet, but AFAICT it successfully builds in the context of the community build, and it's not blocking the rest of the community build from running either.

Or did I misjudge what's happening here?

[milessabin]

@sjrd maybe I misunderstood. I got the impression that there was quite a lot of work to do to prepare an sjs release for 2.13.0-M1.

[milessabin]

@lrytz I had missed the list of community projects. I suspect there won't be a lot of additions to that until there's an sjs release available.

[SethTisue]

I had missed the list of community projects

(It didn't exist yet at the time the M1 announcement went out, so that's understandable.)

[sjrd]

@milessabin There is still some work, but nothing that prevents the part that is run during the community build from building. That we had to fix on the go as breaking PRs got merged in scala/scala, precisely because we don't want to break the community build.

Right now we're blocked ourselves because we need a release of scala-parallel-collections for 2.13.0-M1.

[lrytz]

scala-parallel-collections 0.1.2 is now on the way to maven central

[sjrd]

Status for Scala.js: https://github.com/scala-js/scala-js/milestone/44
The contents of the v0.6.16 milestone were considerably trimmed down to speed up the release ASAP. All issues have pending PRs now, except scala-js/scala-js#2717, which I'll do tomorrow.

A release can be expected by the end of the week.

[xeno-by]

Is anyone here blocked by the absense of a scalameta release? We can probably produce a build once scala.js is out, but if we could, we would rather stick to supporting just 2.11.x and 2.12.x. /cc @olafurpg

[SethTisue]

@xeno-by the only project in the Scala (2.12) community build that depends on scalameta is scalafix. so I wouldn't worry about publishing for 2.13 right now

what might be more worthy of your effort right now, though, would be getting scalameta re-added to the Scala 2.13 community build, since that would only take code changes at your end, not going through publishing nonsense. I opened a ticket here: scala/community-build#533

[lrytz]

The contents of the v0.6.16 milestone were considerably trimmed down to speed up the release ASAP

Thanks! I wonder: in a cross-version build, is it problematic if Scala.js is upgraded to (the trimmed down) 0.6.16 for all Scala versions, or should 2.11 / 2.12 stay on 0.6.15? If so, how can that be done in sbt?

[sjrd]

Scala.js is always backward source and binary compatible in minor versions so no it is not problematic to upgrade Scala.js for all Scala versions.

Anyway I don't think there is a way to upgrade it only for one Scala version.

[sjrd]

When I say "trimmed down" I mean that a bunch of issues and features that were scheduled for 0.6.16 have been reassigned to 0.6.17. In no event are we publishing a 0.6.16 that would be "less" than 0.6.15, obviously.

[lrytz]

Ah, that's the part I misunderstood. Thanks!

[sjrd]

Scala.js 0.6.16 is now available on Maven Central, and supports 2.13.0-M1.
It's not really announced yet though (release notes are not written, and stuff like that), but you can start using it to unblock the eco-system.

It's completely {source,binary} {forward,backward} compatible with 0.6.15.

[lrytz]

Thanks, Sebastien! Both scala-xml and scala-parser-combinators built successfully with 2.13.0-M1.