Skip to content

Commit bf8f85f

Browse files
authored
Merge pull request #1790 from majk-p/patch-1
Update 2022-08-17-long-term-compatibility-plans for LTS vs Next guide
2 parents 37767b2 + b24e163 commit bf8f85f

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

blog/_posts/2022-08-17-long-term-compatibility-plans.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,11 @@ Scala 3 guarantees backward compatibility between all releases and forward compa
3030

3131
## What version of Scala should I use?
3232

33-
So, we know what output compatibility is and what Scala 3 guarantees. What does it mean in practice? What version of the compiler should I choose for my project? The compiler team believes that the good answer for this question is always *the newest one*.
33+
So, we know what output compatibility is and what Scala 3 guarantees. What does it mean in practice? What version of the compiler should I choose for my project?
34+
35+
The simple answer is:
36+
* The **Scala Next** line should be used be used by most users, as it contains the latest features, bug fixes and improvements.
37+
* The **Scala LTS** line is advised to be used for publishing libraries. (Some especially conservative users might also choose it over Scala Next.)
3438

3539
We believe that you should treat the compiler as one of your dependencies. If you are fine with updating the versions of your library dependencies, there should be no reason not to update the compiler version. In most cases, you wouldn't even notice that the Scala version has changed. Meanwhile, you can get better compilation performance, improved error messages, and most importantly, you may be able to use newly stabilized features of the language and of the standard library.
3640

0 commit comments

Comments
 (0)