Top GitHub Comments
Well, the compelling reason is that consumers of the library can prepare their transition to Scala 2.13.0. If not for M5, a good point will be RC1. Since Scala 2.13.0 comes with API change (new collections), the transition process is a bit more work than just relying on source compatibility. Identifying problems with the new collections API early will be generally helpful. Thanks!
code review + merge + snapshot publish.
Just want to re-iterate that we’d be open to this. We actually publish snapshots on each master merge so all we’d need to do is get this building in master.