This thread is for updates and discussions about the upcoming Scala 2.12.17 release.
Scala 2.12.16 (released June 10) included one regression. A fix has already been merged, and we said we’d release that fix in no less than “2–3 months”.
If you’re aware of anything else you think ought to be considered a blocker for this release, please let us know, either by commenting on the appropriate ticket or PR, or by replying on this thread.
At present there are no known blockers and no open issues or PRs on the 2.12.17 milestones in scala/bug and scala/scala.
The most significant changes already merged are listed here:
If you’re aware of anything else you think ought to be considered a blocker for this release
If https://github.com/scala/scala/pull/10064 gets merged for 2.13.9, it would be nice to have it backported in time for 2.12.17 too, for consistency and ease of cross-compilation.
For 2.12.17, we may upgrade scala-compiler’s dependency on scala-xml 1.x to 2.x. Please join the discussion at https://github.com/scala/bug/issues/12632 if you want to say something for or against this proposed change.
We believe we have now merged the last 2.12.17 PR. The milestones are closed. The release-candidate nightly is 2.12.17-bin-45183fa, and it’s green in the community build.
Scala Native 0.4.7 has no problems with supporting 2.12.17-bin-45183fa.
However, I’ve some problems with tests involving collecting java.lang.ref.WeakReference instances. In a single test compiled with 2.12.17 fails. The test does finish successfully using the 2.12.16 or 2.13.9 candidates. It might be an issue related to our GC implementation, and I don’t see a reason why it should lead to a delay in the release.
