graphene/ROADMAP.md
Mel van Londen 4170e73251
Update roadmap (#1019)
* update roadmap

* Update ROADMAP.md graphql-core-next table entry

Co-Authored-By: Jonathan Kim <jkimbo@gmail.com>

* Update ROADMAP.md graphql-core table entry

Co-Authored-By: Jonathan Kim <jkimbo@gmail.com>

* Update ROADMAP.md remove SDL schema creation

* Update ROADMAP.md remove connections structure

* fix trailing whitespace
2019-06-24 20:38:45 -07:00

4.8 KiB

GraphQL Python Roadmap

In order to move Graphene and the GraphQL Python ecosystem forward it's essential to be clear with the community on next steps, so we can move uniformly.

👋 If you have more ideas on how to move the Graphene ecosystem forward, don't hesistate to open a PR

Now

  • Continue to support v2.x with security releases
  • Last major/feature release is cut and graphene-* libraries should pin to that version number

Next

New features will only be developed on version 3 of ecosystem libraries.

Core-Next

Targeted as v3 of graphql-core, Python 3 only

Graphene

  • Integrate with the core-next API and resolve all breaking changes
  • GraphQL types from type annotations - See issue
  • Add support for coroutines in Connection, Mutation (abstracting out Promise requirement) - See PR

Graphene-*

  • Integrate with the graphene core-next API and resolve all breaking changes

*-graphql

  • Integrate with the graphql core-next API and resolve all breaking changes

Ongoing Initiatives

  • Improve documentation, especially for new users to the library
  • Recipes for “quick start” that people can ideally use/run

Dependent Libraries

Repo Release Manager CODEOWNERS Pinned next/master created Labels Standardized
graphene ekampf
graphql-core Cito N/A N/A
graphql-core-next Cito N/A N/A
graphql-server-core Cito
gql ekampf
gql-next ekampf N/A N/A
...aiohttp
...django mvanlonden
...sanic ekampf
...flask
...webob
...tornado ewhauser PR created
...ws Cito/dfee
...gae ekampf PR created
...sqlalchemy jnak/Nabell
...mongo
...relay-py Cito
...wsgi