A couple weeks ago I published https://www.scala-lang.org/2019/01/18/community-build.html which covers a whole year of community build work.
The following covers just what’s been happening in December & January.
I just closed out a round of work on the 2.12 build, with an eye toward setting it aside for a while to focus on 2.13.
new 2.12 additions:
- mdoc (“mdoc is a markdown documentation tool for Scala inspired by tut”; see https://scalameta.org/mdoc/blog/2018/12/30/v1.html)
- sconfig (Lightbend Config converted from Java to Scala, so it can work with Scala.js and Scala Native)
- coverage of Play expanded (https://github.com/scala/community-builds/pull/819; possible further Play and Lagom expansion is under discussion at https://github.com/scala/community-builds/issues/846)
- many tweaks and fixes
One remaining open loop is scala-pet-store (https://github.com/scala/community-builds/pull/835), a Typelevel sample app. Their flagship sample app, I think. In the community build we mostly do libraries, not apps, but we like to include a few apps here and there, for diversity, and to verify that everything works together.
As before, the 2.12 build remains unfrozen primarily because of 2.13, counterintuitively. We need the 2.13 build to validate 2.13; the 2.13 build needs to include the branches where 2.13 upgrades are happening; the easiest way to do that is to get those branches green in 2.12 first.