If this is a poll, then I would vote for a photo of the “compiler team” and/or Scala center slummers and staff in a semi-casual setting. Perhaps there is one meeting at which everyone convenes. A professional photographer could be hired to document the informal occasion.
The cast or dramatis personae is always revolving, so it would be nice to have a snapshot of the people involved. Of course, there are additional contributors from around the globe, and this proposal is not intended to slight them.
A different idea would be to illustrate a major feature of the release with a photo of the team or SIP committee discussing how it should work, in the style of the famous meme where someone is throwing a chair.
5 Likes
The release page doesn’t contain the descriptions about gradle and the scala maven plugin.
That section was mostly introduced due to possible problems that we’ve found out during development and were aware of. Not all build tools must have been affected at all.
For example there was no changes required to support Scala 3.8 in Bazel rules, beside standard procedure and adjusting the tests/CI or used JDK version.
As a compiler team we’re also not able to test out all existing build tools, especially when the big three of sbt, mill, scala-cli covers +99% of Scala 3 projects existing in Scaladex and tested using Scala 3 Open Community Build
If you’re aware if Gradle or Maven plugin requires some new version to work with Scala 3 feel free to link these here to help other users if needed.
1 Like
Postmortem on Scala 3.8.0: Postmortem of scala/scala3#24994 | The Scala Programming Language
We are also working on a 3.8.2 release which will include a fix for SIP-62 better for `dropForMap` phase bug · Issue #24673 · scala/scala3 · GitHub , which can cause some for comprehensions to behave incorrectly at runtime.
3 Likes