[2024-12-05] GraphQL.js support policy

[benjie]

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

[benjie]

@JoviDeCroock please comment (e.g. with 👋) so I can assign this issue to you. Let me know when the item is complete :)

[JoviDeCroock]

All right, been giving this some thought already! :)

[JoviDeCroock]

What I've currently settled on, opinions are very much appreciated

## Version Support

GraphQL.JS follows Semantic Versioning (SemVer) for its releases. Our version support policy is as follows:

- Latest Major Version: We provide full support, including bug fixes and security updates, for the latest major version of GraphQL.JS.
- Previous Major Version: We offer feature support for the previous major version for 12 months after the release of the newest major version.
  This means that for 12 months we can backport features for specification changes _if_ they don't cause any breaking changes. We'll continue
  supporting the previous major version with bug and security fixes
- Older Versions: Versions older than the previous major release are considered unsupported. While the code remains available,
  we do not actively maintain or provide updates for these versions.
  One exception to this rule is when the older version has been released < 1 year ago, in that case we
  will treat it like a "Previous Major Version".

## Long-Term Support (LTS)

We do not currently offer a Long-Term Support version of GraphQL.JS. Users are encouraged to upgrade to the latest stable version
to receive the most up-to-date features, performance improvements, and security updates.

## End-of-Life (EOL) Schedule

We will announce the EOL date for a major version at least 6 months in advance.
After a version reaches its EOL, it will no longer receive updates, even for critical security issues.

## Upgrade Assistance

To assist users in upgrading to newer versions:

- We maintain detailed release notes for each version, highlighting new features, breaking changes, and deprecations.
- Our documentation includes migration guides for moving between major versions.
- The community forum (Discord) is available for users who need additional assistance with upgrades.

## Security Updates

We prioritize the security of GraphQL.JS:

- Critical security updates will be backported to the current and previous major version.
- For versions that have reached EOL, we strongly recommend upgrading to a supported version to receive security updates.

## Community Contributions

We welcome community contributions for all versions of GraphQL.JS. However, our maintainers will primarily focus on reviewing
and merging contributions for supported versions.

[phryneas]

Version Support

GraphQL.JS follows Semantic Versioning (SemVer) for its releases. Our version support policy is as follows:

• Latest Major Version: We provide full support, including bug fixes and security updates, for the latest major version of GraphQL.JS.
• Previous Major Version: We offer feature support for the previous major version for 12 months after the release of the newest major version.

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.

This means that for 12 months we can backport features for specification changes if they don't cause any breaking changes. We'll continue
supporting the previous major version with bug and security fixes

• Older Versions: Versions older than the previous major release are considered unsupported. While the code remains available,
  we do not actively maintain or provide updates for these versions.
  One exception to this rule is when the older version has been released < 1 year ago, in that case we
  will treat it like a "Previous Major Version".

Long-Term Support (LTS)

We do not currently offer a Long-Term Support version of GraphQL.JS. Users are encouraged to upgrade to the latest stable version
to receive the most up-to-date features, performance improvements, and security updates.

End-of-Life (EOL) Schedule

We will announce the EOL date for a major version at least 6 months in advance.

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.

After a version reaches its EOL, it will no longer receive updates, even for critical security issues.

Upgrade Assistance

To assist users in upgrading to newer versions:

• We maintain detailed release notes for each version, highlighting new features, breaking changes, and deprecations.
• Our documentation includes migration guides for moving between major versions.
• The community forum is available for users who need additional assistance with upgrades.

"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?

Security Updates

We prioritize the security of GraphQL.JS:

• Critical security updates will be backported to the current and previous major versions.

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?

• For versions that have reached EOL, we strongly recommend upgrading to a supported version to receive security updates.

Community Contributions

We welcome community contributions for all versions of GraphQL.JS. However, our maintainers will primarily focus on reviewing
and merging contributions for supported versions.

[JoviDeCroock]

Updated variant

## Version Support

GraphQL.JS follows Semantic Versioning (SemVer) for its releases. Our version support policy is as follows:

- Latest Major Version: We provide full support, including bug fixes and security updates, for the latest major version of GraphQL.JS.
- Previous Major Version: We offer feature support for the previous major version for 12 months after the release of the newest major version.
  This means that for 12 months we _can_ backport pull requests for specification changes _if_ they don't cause any breaking changes. We'll continue
  supporting the previous major version with bug and security fixes
- Older Versions: Versions older than the previous major release are considered unsupported. While the code remains available,
  we do not actively maintain or provide updates for these versions.
  One exception to this rule is when the older version has been released < 1 year ago, in that case we
  will treat it like a "Previous Major Version".

## Long-Term Support (LTS)

We do not currently offer a Long-Term Support version of GraphQL.JS. Users are encouraged to upgrade to the latest stable version
to receive the most up-to-date features, performance improvements, and security updates.

## End-of-Life (EOL) Schedule

We will announce the EOL date for a major version at least 6 months in advance.
After a version reaches its EOL, it will no longer receive updates, even for critical security issues.

## Upgrade Assistance

To assist users in upgrading to newer versions:

- We maintain detailed release notes for each version, highlighting new features, breaking changes, and deprecations.
- Our documentation includes migration guides for moving between major versions.
- The [community forum (Discord)](https://graphql.org/community/resources/official-channels/) is available for users who need additional assistance with upgrades.

## Security Updates

We prioritize the security of GraphQL.JS:

- Critical security updates will be backported to the versions within the support window.
- For versions that have reached EOL, we strongly recommend upgrading to a supported version to receive security updates.

## Community Contributions

We welcome community contributions for all versions of GraphQL.JS. However, our maintainers will primarily focus on reviewing
and merging contributions for supported versions.

[benjie]

@JoviDeCroock is this "ready for review"?

[JoviDeCroock]

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.

[benjie]

This was reviewed and approved at the last WG and has now been implmented