This thread is for updates and discussions about the upcoming Scala 2.13.11 release.
The two main motivations for the release are:
Scala 3.3.0 will be released sometime soon (3.3.0-RC2 is already out), and a new Scala 2.13 release is needed for the TASTy reader to support reading 3.3’s TASTy. (The necessary changes, by Jamie Thompson, have already been merged.)
We aim to release every 3–6 months. 2.13.10 came out on 8 Oct 22, so it’s now been over 4 months which means it’s getting to be time anyway.
The 2.13.11 milestone on GitHub has lists of open and merged PRs for the release. You may wish to filter by the “release-notes” label to see only the most significant changes.
Feel free to use this thread to ask questions and share concerns about the timing and contents of the release.
Oh, I should have mentioned that another reason to do 2.13.11 is to ship JDK 20 support in the optimizer (support was already merged). We should do 2.12.18 at about the same time for the same reason; see the 2.12.18 release planning thread.
We’ve just finished QAing the current 2.13 nightly on JDK 20 and all is well. Our test suite is green and will run nightly on JDK 20 from now on, and the same is true of the Scala 2.13 community build.
We ended up reverting one minor, late-merged PR having to do with the presentation compiler’s handling of tab completion for constructors, because it caused a test failure downstream in Metals in the community build. (reference)
I don’t think we need to reset the 7 day testing countdown, as the reversion merely restores the 2.13.10 status quo in this one small area.
Regardless, if you’re still doing any testing, the new release candidate is 2.13.11-bin-f113b1a.
Obviously we’ll want to fix it for 2.13.12, but how big a problem is it for 2.13.11? Is it an obscure corner case, or will it be encountered commonly? If you feel you have some insight into how many users are likely to be affected, please comment on the ticket.