Stable non-beta release?

[miketheman]

Hi there! We love your efforts on this project, and are curious when we might see a non-beta release?

[erikwrede]

Hey Mike, there's currently no one actively working this project. Happy to assist anyone willing to push this over the finish line!

[kiendang]

Hi @erikwrede what needs to be done for the stable release?

[erikwrede]

@kiendang I have switched to FastAPI when migrating to graphene 3, so I don't have a list of specific issues that need to be addressed.
Since there is no roadmap (I could not find one), it's probably best to limit the stable release to a functioning interface with graphql-core 3/graphene 3 that supports. Everything non-breaking can be pushed back to feature releases thereafter if someone is willing to take care of this library. This is not a must-do, so if you have features ready now, please keep them coming 🙂

As a general rule, required steps would include the following:

• Review the open PRs
• Ensure that we are up to date with the newest major releases of the frameworks
• Triage open issues
• After triaging issues, identify if any breaking changes should be made.
• Update Dependencies
• Test with every web framework we support
• Push either another beta/rc or the release, depending on amount of changes

[kiendang]

Looks doable. I can take a stab at this. Currently I have some free time plus have some side projects that use graphene + flask so would be nice to get this over the line.

[erikwrede]

Awesome! Thanks for offering to help. I've published a message on slack to inform everyone, so that I can grant you access to the repo if you require any. In the meantime, feel free to start (reviews are also relevant without access) & to tag me (or text me on the graphene slack) for reviews or anything else! 🙂