Add update to the 3.1.2 blogpost

scala · Jun 1, 2022 · 376e1e2 · 376e1e2
1 parent db5c9a0
commit 376e1e2
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/blog/_posts/2022-04-12-scala-3.1.2-released.md b/blog/_posts/2022-04-12-scala-3.1.2-released.md
@@ -9,6 +9,8 @@ We are happy to announce the release of Scala 3.1.2. This new release brings a f
 
 ## Configurable Scala output version
 
+**June 2022 Update:** configurable Scala output version turned out to be really hard to maintain and is not solving some of problems it was intended to solve. We have decided to drop it in 3.2 and propose long term support versions instead. You can read more in [the dedicated post]({{ site.baseurl }}/blog/2022/05/30/long-term-compatibility-plans.html).
+
 First and foremost, after months of brainstorming and testing, we are bringing an experimental possibility to configure the Scala output version. This means that the compiler can now generate TASTy files and classfiles in a format used by an older minor version of Scala (which can currently be only 3.0.x) effectively specifying the minimum version of the compiler that is able to read your compiled code.
 
 If you are a library maintainer, you may have faced a dilemma, should you update the Scala version to 3.1 or stay on 3.0. On the one hand, updating would bring you all bug fixes and enhancements from the newest version of the compiler. On the other, all new releases of your library would be unusable for all the users that are, for some reason, stuck on Scala 3.0.