-
Notifications
You must be signed in to change notification settings - Fork 228
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
[2024-12-05] GraphQL.js support policy #1614
Comments
@JoviDeCroock please comment (e.g. with 👋) so I can assign this issue to you. Let me know when the item is complete :) |
All right, been giving this some thought already! :) |
What I've currently settled on, opinions are very much appreciated
|
I would not mention features here. While we can always decide to backport a feature, features are a great way of getting people to actually update. People might stay on older versions for longer because they read this.
Is there a risk that we might forget that and then have to support things for longer than we want?
"Community forum" is a bit ambiguous here - I looked at https://graphql.org/community/resources/official-channels/ and https://graphql.org/community/resources/community-channels/ and don't find a forum. If all of these are meant, maybe reword this, otherwise we just pick one or two of those?
It's not clear how far "and previous major versions" goes here - if this only means those in the support window, maybe add "that are still in the support window" or similar?
|
@JoviDeCroock to write up a policy for version support of GraphQL.js
From the Dec 2024 discussion, we should support:
Minor and patch releases do not extend the support term.
Note: Action Item issues are reviewed and closed during Working Group
meetings.
The text was updated successfully, but these errors were encountered: