Update 2022-08-17-long-term-compatibility-plans for LTS vs Next guide #1790
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Last year the advisory board has accepted https://github.com/scalacenter/advisoryboard/blob/main/proposals/032-scala-version-guidance.md that was later marked as completed in scalacenter/advisoryboard#164 by the introduction of https://scala-lang.org/development. While this page provides a clear guidance, it's very hard to find. I have no idea how to reach this page other than via direct link.
The proposal mentioned inconsistent communication in https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html#what-version-of-scala-should-i-use - an article that is currently number one for most search engine queries for LTS vs Next.
This PR updates the mentioned post, aligning the communication to match the contents of https://scala-lang.org/development