Open
Description
@JoviDeCroock to write up a policy for version support of GraphQL.js
From the Dec 2024 discussion, we should support:
- The two latest major releases
- All major releases published in the previous 2 years
Minor and patch releases do not extend the support term.
- assignee(s): @JoviDeCroock
- source: https://github.com/graphql/graphql-wg/blob/main/notes/2024/2024-12.md
Note: Action Item issues are reviewed and closed during Working Group
meetings.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
benjie commentedon Dec 12, 2024
@JoviDeCroock please comment (e.g. with 👋) so I can assign this issue to you. Let me know when the item is complete :)
JoviDeCroock commentedon Dec 12, 2024
All right, been giving this some thought already! :)
JoviDeCroock commentedon Dec 13, 2024
What I've currently settled on, opinions are very much appreciated
phryneas commentedon Dec 13, 2024
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.
Keep in mind - what we describe here is a minimum guarantee, we can always do more even if it's not written down here.
Is there a risk that we might forget that and then have to support things for longer than we want?
It could also be solely bound to the release of a major version, which might also make it easier to plan for for users.
"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 commentedon Jan 10, 2025
Updated variant
benjie commentedon Jan 11, 2025
@JoviDeCroock is this "ready for review"?
JoviDeCroock commentedon Jan 11, 2025
In my eyes it is yes, happy to adjust where needed, my plan was to bring it up in the graphql-js-wg end of month and then bring it to the general wg.