4 ms·

> Weird to blame current Scala versions for not supporting end of life versions. I didn't. > will not receive any bug fixes or security updates, and Scala 2.1

> Weird to blame current Scala versions for not supporting end of life versions. I didn't. > will not receive any bug fixes or security updates, and Scala 2.11 will not either Oh, I'm pretty sure that Scala 2.11 will receive fixes, security updates and even backports of features for a very long time. For example SI-2712 is getting back-ported to Scala 2.11.9 and there's even talk of back-porting it to Scala 2.10.

paulddraper 10y ago
The last announced plan was to conclude 2.11.x with 2.11.9 (currently at 2.11.8). Maybe we'll see longer support for people who don't migrate (heck, SBT still uses 2.10.x), but justifying it by Java version is weird. If you're okay with using old Java versions, it's not much of a stretch to say you'll be okay with old Scala versions.
- adriaanm 10y ago
  Yep, 2.11.9 is the last planned release, but we would release another one for security fixes or anything as severe. If we get customer requests for backports, we (usually) also release those publicly. Thanks for your support!
- lmm 10y ago
  > If you're okay with using old Java versions, it's not much of a stretch to say you'll be okay with old Scala versions. No, because Scala doesn't offer forward binary or source compatibility. Maintainers of widely-used Java libraries can write and build for Java 6 and be confident their libraries will be usable by everyone (on Android and off). Maintainers of widely-used Scala libraries have no such option (for now they can write their code using the subset that works in Scala 2.11 and 2.12 and cross-build, but there's no guarantee that such a subset will be maintained in 2.13 and beyond).
  - paulddraper 10y ago
    > there's no guarantee that such a subset will be maintained There's no guarantee about Java either. This class compiles with Java 7, but not with Java 8: class SampleClass { static class Baz<T> { public static java.util.List<Baz<Object>> sampleMethod(Baz<Object> param) { return null; } } private static void bar(Baz arg) { Baz element = Baz.sampleMethod(arg).get(0); } } Like Java or any other good software, Scala will try to maintain backwards compatibility (particularly source compatibility).
    - lmm 10y ago
      > There's no guarantee about Java either. This class compiles with Java 7, but not with Java 8: Ok, but you can compile it with the newer compiler by passing -source 1.7, right? And you can call into it from 1.8 code?
      - paulddraper 10y ago
        Yes, binary compatibility is maintained in this case.

paulddraper 10y ago

The last announced plan was to conclude 2.11.x with 2.11.9 (currently at 2.11.8). Maybe we'll see longer support for people who don't migrate (heck, SBT still uses 2.10.x), but justifying it by Java version is weird. If you're okay with using old Java versions, it's not much of a stretch to say you'll be okay with old Scala versions.

adriaanm 10y ago
Yep, 2.11.9 is the last planned release, but we would release another one for security fixes or anything as severe. If we get customer requests for backports, we (usually) also release those publicly. Thanks for your support!
lmm 10y ago
> If you're okay with using old Java versions, it's not much of a stretch to say you'll be okay with old Scala versions. No, because Scala doesn't offer forward binary or source compatibility. Maintainers of widely-used Java libraries can write and build for Java 6 and be confident their libraries will be usable by everyone (on Android and off). Maintainers of widely-used Scala libraries have no such option (for now they can write their code using the subset that works in Scala 2.11 and 2.12 and cross-build, but there's no guarantee that such a subset will be maintained in 2.13 and beyond).
- paulddraper 10y ago
  > there's no guarantee that such a subset will be maintained There's no guarantee about Java either. This class compiles with Java 7, but not with Java 8: class SampleClass { static class Baz<T> { public static java.util.List<Baz<Object>> sampleMethod(Baz<Object> param) { return null; } } private static void bar(Baz arg) { Baz element = Baz.sampleMethod(arg).get(0); } } Like Java or any other good software, Scala will try to maintain backwards compatibility (particularly source compatibility).
  - lmm 10y ago
    > There's no guarantee about Java either. This class compiles with Java 7, but not with Java 8: Ok, but you can compile it with the newer compiler by passing -source 1.7, right? And you can call into it from 1.8 code?
    - paulddraper 10y ago
      Yes, binary compatibility is maintained in this case.