search

scala / scala-dev

Scala 2 team issues. Not for user-facing bugs or directly actionable user-facing improvements. For build/test/infra and for longer-term planning and idea tracking. Our bug tracker is at https://github.com/scala/bug/issues
Apache License 2.0
130 stars 15 forks source link

Release 2.11.13 #451

Closed retronym closed 1 year ago

retronym commented 6 years ago

NOTE: at this point, we are not committing to another 2.11 release -- this is a placeholder to collect TODOs in case we do decide to cut another release.

Motivation:

sjrd commented 6 years ago

Advertising a regression I had found in 2.10.7 and 2.11.12: https://github.com/scala/bug/issues/10609

Note that personally, I don't care whether it's going to be fixed or not; I just disabled the failing test in our test suite. But maybe this affects other people.

mpetruska commented 6 years ago

Might make sense to talk about scala/scala#6195. It causes a Spark-shell issue SPARK-22393. Please note that the changes in that PR are "retrofitted" into Spark-shell (not merged yet), so this is not really a priority.

SethTisue commented 6 years ago

note that publishing 2.11.13 would now require either resurrecting some now-decayed/disabled Jenkins stuff, or backporting the Travis-CI-based publishing from 2.12.x

smarter commented 6 years ago

Crashes due to -Yrangepos validation affect IDE and tooling (e.g. scalameta) users, so it'd make a ton of sense to backport https://github.com/scala/scala/pull/6754

smarter commented 6 years ago

Apparently 2.12 can emit code that causes ambiguous method errors in javac starting with Java 11, this should be fixed by https://github.com/scala/scala/pull/7035. I assume that 2.11 is affected by this and could benefit from a backport.

SethTisue commented 5 years ago

if this happens, we might want to backport the license change to Apache 2 (scala/scala#7314, scala/scala#7407, scala/scala#7730, scala/scala#8015)

SethTisue commented 5 years ago

and undeprecate .linesIterator, as we did in 2.12.8

SethTisue commented 5 years ago

and bump the copyright year to 2019 or whatever. (I'm about to PR this to 2.12.x.)

SethTisue commented 5 years ago

this is only a would-be-nice, but if the 2.11.x REPL could be made to work on JDK 11, without risk of breaking something else, that'd be nice. it's https://github.com/scala/bug/issues/10603

SethTisue commented 5 years ago

this hashmap fix backport PR could be reopened and merged: https://github.com/scala/scala/pull/7522

SethTisue commented 5 years ago

Backport ASM upgrade to fix regression: scala/scala#6180

and https://github.com/scala/scala/pull/7780

adriaanm commented 5 years ago

The ASM 7 upgrade is trickier, but I have a PR for the 6.2 one (scala/scala#8079), which should be enough, as our ambitions for 2.11 don't extend beyond Java 11

SethTisue commented 5 years ago

We should backport https://github.com/scala/scala/pull/8289 (fix Scaladoc generation on JDK 11+, as per https://github.com/scala/bug/issues/11635); I have seen it in the 2.11 community build (grizzled and monix both, in https://scala-ci.typesafe.com/view/scala-2.11.x/job/scala-2.11.x-jdk11-integrate-community-build/155/)

SethTisue commented 5 years ago

~re: ASM upgrade, we should watch out for https://github.com/scala/bug/issues/11667 (unless that proves to be ASM 7 specific, and it sounds like we won't go all the way 7, recording it here regardless just in case)~ [edit: the bug is not related to the asm upgrade]

SethTisue commented 5 years ago

note that we now require Java 8+ on the 2.11.x branch

RussellSpitzer commented 4 years ago

We have seen scala/scala#8289 as well in some of our internal builds (as well as those using Spark)

SethTisue commented 1 year ago

Closing, as this seems unlikely to ever happen, unless somebody threw money at us