The people at Scala have released a postmortem on this https://www.scala-lang.org/blog/2024/03/06/scala-3.3.2-post-mortem.html
On Mon, Mar 4, 2024 at 8:25 AM Matthew de Detrich < matthew.dedetr...@aiven.io> wrote: > We should backport 3.3.3 to the 1.0.x series, just need to be careful > about it. Also > we shouldn't treat Scala versions the same way that we treat Java/JDK > versions, > it is expected that projects eventually update to the latest versions of > Scala in the > minor series because a lot of tooling is built around that, i.e. metals, > scalafix etc etc > require the latest Scala versions to function properly/at their best. > > > With Scala compilation changes, there are pros and cons. We've has 3.3.2 > release nixed due to a bug in that release (relating to Tasty > incompatibilities). So all in all, I don't see any big benefit to this > backfit and I see potential problems too. > > Yes, but the point is that it was caught before an actual release. This is > a good, > not a bad thing after all the whole point of the RC is to catch these > issues in the wild. > The fact that it happened the way it did should increase confidence, not > decrease it. > > On Sun, Mar 3, 2024 at 12:54 PM PJ Fanning <fannin...@apache.org> wrote: > >> I'm a +0 on this (neutral). With regular dependencies, I think we should >> only backport to 1.0.x if they fix a serious bug (including security >> issues) and the upgrade is not a big change. >> >> With Scala compilation changes, there are pros and cons. We've has 3.3.2 >> release nixed due to a bug in that release (relating to Tasty >> incompatibilities). So all in all, I don't see any big benefit to this >> backfit and I see potential problems too. >> >> On 2024/03/01 08:30:59 kerr wrote: >> > It fixes some compiler backend bugs too. >> > And add better support for sbt/metal and coverage. >> > >> > [1] >> > >> https://www.scala-lang.org/blog/2024/02/29/scala-3.4.0-and-3.3.3-released.html >> > [2] https://github.com/lampepfl/dotty/releases/tag/3.3.3 >> > >> > +1 from me. >> > >> > 何品 >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> For additional commands, e-mail: dev-h...@pekko.apache.org >> >> > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Alexanderufer 3-7, 10117 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* matthew.dedetr...@aiven.io
