From 0e0b2e8289679f815b2c501848d5eef7b431222f Mon Sep 17 00:00:00 2001 From: Seth Tisue Date: Wed, 5 Mar 2025 09:30:51 -0800 Subject: [PATCH 1/3] tweaks to JDK 17 blog post --- _posts/2025-03-05-next-scala-lts-jdk.md.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/_posts/2025-03-05-next-scala-lts-jdk.md.md b/_posts/2025-03-05-next-scala-lts-jdk.md.md index f3fec667a..7e8a7d3b4 100644 --- a/_posts/2025-03-05-next-scala-lts-jdk.md.md +++ b/_posts/2025-03-05-next-scala-lts-jdk.md.md @@ -5,12 +5,15 @@ title: "JDK 17 will be the next minimum version required by Scala 3" by: Tomasz Godzik, VirtusLab & Scala Core Team --- -We recently asked for community input about changing the JDK version used by the -Scala 3 compiler. We wanted to thank everyone for their input and announce the +We recently asked for community input on changing the JDK version used by the +Scala 3 compiler. We now thank everyone for their input and announce the decision to switch to JDK 17 as the new minimum, starting with Scala 3.8 minor and the subsequent new LTS which will mostly likely be Scala 3.9. -The discussion didn't uncover any compelling reason not to leave JDK 11 behind. +Our reasoning for dropping 8 was presented in this [previous blog +post](https://www.scala-lang.org/blog/next-scala-lts.html). + +The discussion on whether to also drop 11 didn't uncover any compelling reason not to leave JDK 11 behind. 11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally considered a difficult upgrade for users. 17 offers useful APIs and VM features. In the JVM world, requiring 17+ is already a mainstream position and is becoming more so @@ -19,12 +22,16 @@ we should take this chance to aid open-source maintainers by reducing the testing and maintenance burden across the entire Scala 3 tooling and library ecosystems as much as we reasonably can. +The open discussion that led to this decision can be found at the +[Scala contributors forum](https://contributors.scala-lang.org/t/next-scala-3-lts-version-will-increase-minimum-required-jdk-version). + +## What about Scala 3.3 LTS? + This change only concerns future minor versions of Scala 3. In particular, the Scala 3.3 LTS line is unaffected by this change. Scala 3.3.x releases will continue for at least a year after the new LTS line begins. +## What about Scala 2? + There are no plans to change Scala 2’s JDK support. It will continue being built using JDK 8, as before. - -The open discussion that led to this decision can be found at the -[Scala contributors forum](https://contributors.scala-lang.org/t/next-scala-3-lts-version-will-increase-minimum-required-jdk-version). From 64a6dd9931bbf9f91f69c80c3a21770666d6a6c3 Mon Sep 17 00:00:00 2001 From: Seth Tisue Date: Wed, 5 Mar 2025 09:31:29 -0800 Subject: [PATCH 2/3] fix doubled .md extension --- ...-next-scala-lts-jdk.md.md => 2025-03-05-next-scala-lts-jdk.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename _posts/{2025-03-05-next-scala-lts-jdk.md.md => 2025-03-05-next-scala-lts-jdk.md} (100%) diff --git a/_posts/2025-03-05-next-scala-lts-jdk.md.md b/_posts/2025-03-05-next-scala-lts-jdk.md similarity index 100% rename from _posts/2025-03-05-next-scala-lts-jdk.md.md rename to _posts/2025-03-05-next-scala-lts-jdk.md From 6bcf9209757261f12447dd82f4adbfa65874674c Mon Sep 17 00:00:00 2001 From: Seth Tisue Date: Wed, 5 Mar 2025 09:33:24 -0800 Subject: [PATCH 3/3] add even more headers --- _posts/2025-03-05-next-scala-lts-jdk.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_posts/2025-03-05-next-scala-lts-jdk.md b/_posts/2025-03-05-next-scala-lts-jdk.md index 7e8a7d3b4..44291378a 100644 --- a/_posts/2025-03-05-next-scala-lts-jdk.md +++ b/_posts/2025-03-05-next-scala-lts-jdk.md @@ -10,9 +10,13 @@ Scala 3 compiler. We now thank everyone for their input and announce the decision to switch to JDK 17 as the new minimum, starting with Scala 3.8 minor and the subsequent new LTS which will mostly likely be Scala 3.9. +## Why drop 8? + Our reasoning for dropping 8 was presented in this [previous blog post](https://www.scala-lang.org/blog/next-scala-lts.html). +## Why drop 11? + The discussion on whether to also drop 11 didn't uncover any compelling reason not to leave JDK 11 behind. 11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally considered a difficult upgrade for users. 17 offers useful APIs and VM features. In the JVM