It's time for the annual blog post

[SethTisue]

previously:

• https://www.scala-lang.org/2018/01/16/community-build-growth.html
• https://www.scala-lang.org/2019/01/18/community-build.html

I just updated README.md to include links to my news posts on contributors.scala-lang.org, so I can start by just mashing those together into a single update

topics to cover:

• the main thing is to say, this is now basically done. “We now believe the Scala 2.13 community build is sufficiently large and sufficiently up-to-date to suffice for the needs of the 2.13.x series for the rest of its lifetime", something like that. the build will continue to receive minor updates and maintenance but for the most part, our work here is done.
• what projects we've added since the last post
• perhaps include a story or two about how the build has helped us recently
• talk about Scala Steward, perhaps
• what’s happening with JDK 11, 13, 14?
  • the big change is that the 2.13.x-on-11 build is now 100% green and the 2.13.x-on-14 build now has only a handful of failures
  • this is partly because of work that I did
  • but really mainly because the community has been adding OpenJDK 11, especially, to their own CI matrices, that's considered pretty standard now
  • but note people still publish from 8. I have only seen one project (fs2) switch to 11 as their main build
• 2.11 build is frozen, 2.12 build is mostly frozen, even in the 2.13 build freezing is increasingly becoming the default
• what’s happening with Scala 2.13?
  • maybe take a little victory lap that there have been so few issues with 2.13 that the 2.13.1 and 2.13.2 releases ended up widely spaced because there wasn't anything super urgent/serious to fix. the community build is one of the reasons this has gone so well.
• we're on AdoptOpenJDK now

[SethTisue]

draft PR at https://github.com/scala/scala-lang/pull/1113 , feedback very welcome

[SethTisue]

publishing next week