Closed adriaanm closed 5 years ago
Migrating anything that is an sbt and Zinc dependency would help so that we can publish a 2.13 version of the incremental compiler before the release of the RC. We're currently blocked by:
I'd like to nominate scala-parallel-collections. ;)
Haha, of course the parallel collections were already on the list :-)
as usual, https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md lists published projects and has links to open tickets for projects that haven't published yet
Are macwire, com.softwaremill.common:tagging, circe, circe-derivation, twilio's guardrail, sttp, gradle-scoverage, gradle-scalastyle-plugin, wartremover, sangria, and gatling already tracked?
https://github.com/twitter/util could probably use some help, and is often a deep transitive dependency
Any guide to port a project from 2.12 to 2.13 ?
I'm willing to work on Apache Spark.
Get the dependents:
$ ./build/mvn -Phive-thriftserver -DskipTests package
$ ls assembly/target/scala-2.12/jars | grep _2.12 | grep -v spark
Well, Apache Spark depends on ...
@sadhen's suggestions are great. I would prioritize those deps to make sure we don't repeat the same mistake with Apache Spark in 2.13. Even if it's not going to be released this year, the closer we are from having a working 2.13 Apache Spark port available, the better.
(I don't know how much does Spark use Scala collections, but if it does I also think it would be a good real-world use case to assess the performance of the new collections.)
If you're porting code to 2.13, check out the presentation on this topic by @julienrf and myself from ScalaDays. For the new collections library we have an updated documentation on scala-lang. For cross-building on 2.12 and 2.13 you may want to use the collection-compat library.
It looks like https://github.com/scala/bug/issues/11030 is preventing fs2 and probably other projects from compiling with 2.13: https://github.com/functional-streams-for-scala/fs2/issues/1232, so fixing it would definitely count as helping the ecosystem migrate :).
Gatling request: https://github.com/gatling/gatling/issues/3566
We have a ticket for scala-swing now:
I'd certainly like to see help for Scala-Native. Getting to 2.12 seems to be the big challenge for them. Hopefully 2.12 => 2.13 will be relatively straightforward.
volunteer to port boopickle? it's blocking http4s and gatling (and perhaps other projects)
For spark here is the dependency tree (no profile used, we need to verify with profiles to see what they bring in). Verified @sadhen's list. Pending issues:
Spire depends on Algebra which doesn't have a 2.13 release yet. WIP here: https://github.com/typelevel/algebra/pull/226
See also https://github.com/scalacommunitybuild/algebra/tree/community-build-2.13 (and generally, the same pattern of branch name in that org for many projects)
FYI, 2.13.0-RC2 is tagged and on Maven Central! We'll announce after the weekend.
For chill & breeze, we should start with twitter-util and scrooge, which are already in the community build. To see the errors, grep for [twitter-util] [error]
in https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-community-build/2208/consoleText.
I have a WIP for twitter-util at https://github.com/twitter/util/pull/248 -- would particularly appreciate ideas for https://github.com/twitter/util/pull/248/files#r279409022
Looks like monadless isn't in the community build. There's a question about 2.13 support here: https://github.com/monadless/monadless/issues/9
Any reason scalamock is not pointing to https://github.com/paulbutcher/ScalaMock ?
over at https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md I'm not really doing any more maintenance on the list of what is published for 2.13 (except merging PRs on it), but I am definitely maintaining the list of "please publish for 2.13" tickets at https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md#pending, so that's a place to look for projects to help upgrade
For spark here is the dependency tree (no profile used, we need to verify with profiles to see what they bring in). Verified @sadhen's list. Pending issues:
Spire has a 0.17.0-M1 release which is available for Scala 2.13
this is an open-ended/never-ending task, but I think this ticket has now served its purpose. thanks all!
I'm continuing to maintain https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md — it lists projects that are known not to support 2.13 yet
@rafalmag I added the link to https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md
We at Lightbend are seeking to collaborate with OSS project maintainers to help port projects from 2.12 to 2.13. This ticket serves to coordinate the effort -- please comment here with any projects you'd like to nominate (including your own ;-)).