Seems like there’s a good chance we’ll have a release candidate by today or tomorrow. (And once we designate a candidate, we’ll let at least two weeks pass for testing before final release.)
We believe we have now merged the last 2.12.16 PR. The milestones are closed. The release-candidate nightly is 2.12.16-bin-c850a83, and it’s green in the community build.
2.12.16 is now on Maven Central. Please publish compiler plugins, tooling, etc!
As usual, the release will not be widely announced until a few days have passed and important downstream projects have published. I’m hoping to announce first thing Friday (U.S. Pacific time).
We (Lukas and I) propose to list it as a known issue in the 2.12.16 release notes, but not withdraw the release over it. Our reasoning is that the problem occurs at compile-time (far less pernicious than a runtime failure) and will only affect certain users with mixed Scala/Java codebases with a certain kind of Java code.
But is significant enough that we should build 2.12.17 sooner rather than later — 2–3 months, say, rather than the 6–9 month gap we sometimes have in mature release lines.