The Scala 3 standard library is once again accepting contributions after a long freeze, with the scala/scala3 GitHub repository now the primary place to propose changes. API-affecting changes must follow a documented contribution process, while purely internal changes go through the standard pull request flow. Backporting improvements to Scala 2 will be rare, with most new functionality requiring migration to Scala 3. The Scala Core Coordinator oversees this process.
Questions this post answers
How do I contribute a change to the Scala 3 standard library now?
Submit changes to the scala/scala3 GitHub repository, which is now the main place for standard library contributions after a long freeze. API-affecting changes must follow the documented stdlib contribution process outlined in the repository's contributing guide, while purely internal changes use the standard pull request process. The Scala Core Coordinator oversees the overall process. daily.dev surfaces open-source process changes like this for developers tracking how to contribute to Scala.
Can new Scala 3 standard library features be backported to Scala 2?
Backporting is possible but will be the exception rather than the norm. Most new standard library functionality will only be available by migrating to Scala 3, rather than being ported back to Scala 2. daily.dev helps developers weighing a Scala 2 to Scala 3 migration stay on top of related changes.