Core Team Meeting Notes

Announcements
1

On last Scala Core team meeting we decided to start publishing the meeting notes for each of the meetings. This thread will serve as a place to publish them and will be locked to other comments. If you want to discuss a particular point you can always open a separate topic.

If there are any issues related to the compiler that you want to have on the agenda you can always propose them, but decision to include them will be up to the people in the core team. Most likely we will not include any simple matters and only focus on topics that need an actual decision or discussion.

I will follow up with the most recent meeting notes in a bit.

10 Likes
3

Core team meeting 12.08.2026

Attendees:

  • Piotr Chabelski as Product Manager

  • Martin Odersky

  • Oliver BraÄŤevac as LAMP Representative

  • Wojciech Mazur as Scala Native Representative, Release Officer and CB Maintainer

  • Tomasz Godzik as Coordinator and VirtusLab Representative

  • Lukas Rytz as Scala 2 Maintainer

  • Seth Tisue as Community Advocate

  • SĂ©bastien Doeraene as Scala.js Representative

Guests:

  • MikoĹ‚aj Fornal

Topics:

  1. https://github.com/scala/scala3/pull/26497 who can help out with getting java records pattern matching reviewed for 3.10?

  2. Releases status and discussion.

  3. https://contributors.scala-lang.org/t/proposal-fixing-null-methodofany-under-explicit-nulls/7504 and its PR https://github.com/scala/scala3/pull/26771 (from Seb)

  4. Should we post meeting notes in a public capacity? (from Tomasz)

  5. Should add a section about backporting to LTS? (by default it’s best effort, but for important fixes we could do max effort)

Postponed

  1. SLC: Automatic conversion to Option https://contributors.scala-lang.org/t/slc-conversion-a-option-a/7514/37

  2. https://github.com/scala/scala3/pull/26668 Tighten rules for implicit conversions

Conclusions:

  1. Lukas Rytz will take a look at the PR and review it.

  2. There are a number of potential regressions in 3.10 that need to be looked at. Some of them are expected due to recent changes and fixes, but we will need to make sure none of them are unexpected.

  3. The approach was accepted and the PR can be merged.

  4. We will post the meeting notes on the contributors forum.

  5. We will add a note to the PR template and mention this to the compiler team.

1 Like