Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sangria 2.0.0 planning and timeline #463

travisbrown opened this issue Nov 1, 2019 · 4 comments


Copy link

@travisbrown travisbrown commented Nov 1, 2019

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


This comment has been minimized.

Copy link

@vasantteja vasantteja commented Nov 1, 2019

Hi, please let me know if you want help with any coding help. I am interested to contribute.


This comment has been minimized.

Copy link

@jregistr jregistr commented Nov 2, 2019

I'd like to suggest we adopt Vs Code's pattern for planning/exposing the work that is in progress for the next planned release. The idea is to have a central place where we mention what is being considered/worked on for the next release.
Take a look at Vs Code's October IterationPlan for example.
But following this, I'd imagine we'd come up with something below 👇. Alternatively, we could use Github projects for issue status and an issue for related discussion and updates.

I would be happy to get some thoughts on this.

This issue captures the work in the planned release 2.0.0. The planned release date for this update is November 22.

Legend for description markers.

Mark Description
🛠 Work in progress
⚠️ Blocked task
🚧 Deferred task for next iteration
💪 Being considered but work has not started
🔴 Missing issue reference
🔵 More investigation required to remove uncertainty

Scala Version Update

  • 🛠 Support Scala 2.13 #440

Spec Update

  • 🛠 Support repeatable directives. #409

Update: 04/11/2019

Release candidate(s) are now available.


This comment has been minimized.

Copy link

@dhoepelman dhoepelman commented Nov 2, 2019

the final module, sangria-rxscala, is only waiting on RxScala to add 2.13 support

Scala 2.13 support is done, but unfortunately not released. I've opened an issue about this, hopefully a release can be made or I can get rights to do it.


This comment has been minimized.

Copy link

@travisbrown travisbrown commented Nov 4, 2019

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.