I think beta-support will be good. I am ok to trade stability for being able to use 2.12-only libraries in my code and if there is something mission-critical nobody will block from using stable 2.11
Sincerely, Anton Kulaga Bioinformatician at Computational Biology of Aging Group 296 Splaiul Independentei, Bucharest, Romania, 060031 http://aging-research.group On Fri, 31 Aug 2018 at 00:38, shane knapp <skn...@berkeley.edu> wrote: > +1 on beta support for scala 2.12 > > On Thu, Aug 30, 2018 at 2:33 PM, Stavros Kontopoulos < > stavros.kontopou...@lightbend.com> wrote: > >> +1 that would be great Sean, also you put a lot of effort in there, would >> make sense to wait a bit. >> >> Stavros >> >> On Fri, Aug 31, 2018 at 12:00 AM, Sean Owen <sro...@apache.org> wrote: >> >>> I know it's famous last words, but we really might be down to the last >>> fix: https://github.com/apache/spark/pull/22264 More a question of >>> making tests happy at this point I think than fundamental problems. My goal >>> is to make sure we can release a usable, but beta-quality, 2.12 release of >>> Spark in 2.4. >>> >>> On Thu, Aug 30, 2018 at 3:56 PM antonkulaga <antonkul...@gmail.com> >>> wrote: >>> >>>> >There are a few PRs to fix Scala 2.12 issues. I think they will keep >>>> coming >>>> up and we don't need to block Spark 2.4 on this. >>>> >>>> I think it can be better to wait a bit for Scala 2.12 support in 2.4 >>>> than to >>>> suffer many months until Spark 2.5 with 2.12 support will be released. >>>> Scala >>>> 2.12 is not only about Spark but also about a lot of Scala libraries >>>> that >>>> stopped supporting Scala 2.11, if Spark 2.4 will not support Scala 2.12, >>>> then people will not be able to use them in their Zeppelin, Jupyter and >>>> other notebooks together with Spark. >>>> >>>> >> >> >> >> > > > -- > Shane Knapp > UC Berkeley EECS Research / RISELab Staff Technical Lead > https://rise.cs.berkeley.edu >
