Scala homepage should make LTS clearer?

But ideally all serious tooling should have been updated before the public release of a new version. And if that’s not feasible for a specific tool it should warn you to delay updating until it’s caught up, which shouldn’t be very long.

1 Like

Perhaps a good solution would be to have LTS not be a branch so much as a rolling version tag, perhaps with a less confusing name.

“Edge” would be the most current version that has been released.
“Stable” would be the most current version that has full support in a blessed subset of the tooling (at least Mill, Sbt, Metals, Scalafmt, Intellij, Scalafix, and VSCode), and gets bumped as quickly as the tooling catches up.

This way we can point newcomers and those with lower tolerance for tooling shenanigans at the most recent version that will provide them the experience they need, and still keep them as close to up to date as possible.

It would also provide a way to easily track the current state of tooling support.

It’s refreshing to see the community come together for an invigorating discussion!

My understanding is that LTS does not mean “left to rot” but “Left To Stew”.

That is, left to Scala Steward to keep updated.

It would be helpful if the Steward submitted PRs for -source:LTS-migration -rewrite.

1 Like

That is true, we only use LTS at work. And I think Scala should publish a LTS update release along with a Next Scala, we should publishing the LTS release more regularly.

LTS are published every 6 weeks

1 Like