Sangria 2.0.0 planning and timeline

Last week we recovered access to the org.sangria-graphql group and published a Sangria 2.0.0-M1 milestone release with support for Scala 2.13, together with releases for most of Sangria’s marshalling and streaming modules. Since then we’ve also published releases with 2.13 support for seven of the eight remaining modules (the final module, sangria-rxscala, is only waiting on RxScala to add 2.13 support).

The next step is deciding on what still needs to be done for the 2.0.0 release. There are several open pull requests that still need review, prioritization, and migration to the new GitHub organization, and dozens of open issues. I’ve created a 2.0.0 milestone in the new GitHub organization for tracking preparation for this release, and have migrated one of Oleg’s pull requests that seems like it should be included.

We’ll also need to decide on an approximate timeline for the release. I’d propose that we aim to have the milestone list finalized by the end of next week (November 8), and to leave a couple of weeks for implementation and testing (possibly including a 2.0.0-M2 release) after that, with November 22 as a target date for the 2.0.0 release. That would give us a full month between the first milestone and the final release.

In the meantime it would be extremely helpful for adopters to try out 2.0.0-M1 and the accompanying module releases and to report back here with any feedback.

/cc @felipesilva @sachee @yanns

[yanns]

Release 2.0.0 is out 🥳 https://github.com/sangria-graphql/sangria/releases/tag/v2.0.0

[travisbrown]

@jregistr I’m personally reluctant to add a lot of new process here, primarily because I’m not sure anyone has capacity to own it, but also because I don’t think there’s much risk of duplicating work now that the initial round of 2.13 updates is done.

In my view our main goal should be to make sure that people who have opened (or reviewed) PRs or issues are aware of the move and the timeline and can advocate for the changes if they’re still interested. If someone wants to volunteer to help with more formal coordination, though, we should definitely discuss it!