chore(docs): Update Gatsby framework version support information (#33825)

Co-authored-by: Lennart <[email protected]>
Co-authored-by: gatsbybot <[email protected]>

Author: 3 people

README.md

@@ -147,6 +147,8 @@ We welcome suggestions for improving our docs. See the [“how to contribute”]
 
 Wondering what we've shipped recently? Check out our [release notes](https://www.gatsbyjs.com/docs/reference/release-notes) for key highlights, performance improvements, new features, and notable bugfixes.
 
+Also, read our [documentation on version support](https://www.gatsbyjs.com/docs/reference/release-notes/gatsby-version-support/) to understand our plans for each version of Gatsby.
+
 ## 💼 Migration Guides
 
 Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v4 to your site without starting from scratch!

docs/docs/reference/release-notes/gatsby-version-support.md

@@ -0,0 +1,38 @@
+---
+title: Gatsby Framework Version Support
+---
+
+## Introduction
+
+This page illustrates the support plans for the major versions of Gatsby. This allows you to effectively plan your Gatsby framework upgrades.
+
+Generally, you can expect **1 major version per calendar year**. Although, there may be more than 1 major per year when a necessary evolution of Gatsby requires significant breaking change.
+
+## Release and support schedule
+
+Note: Future time ranges are listed when a specific target date is not yet determined.
+
+| Version | Status                        | As Of            | Until           |
+| ------- | ----------------------------- | ---------------- | --------------- |
+| 4       | Active                        | October 21, 2021 | Summer 2022     |
+| 3       | Maintenance Long-term support | October 21, 2021 | Summer 2022     |
+| 2       | Maintenance Long-term support | March 3, 2021    | January 1, 2022 |
+
+## Terminology
+
+- **Critical Patch** - A critical patch addresses an issue that prevents the Gatsby framework from delivering intended user value under typical conditions. Other items, such as minor bug fixes and new features are not considered "critical patches" to Gatsby.
+
+- **Active Long-Term Support** - Receives priority attention from the core maintainers of Gatsby. New features to Gatsby are only available in the Active Long-Term Supported version.
+
+- **Maintenance Long-term Support** - Receives critical patches, but does not receive new features.
+
+- **Unsupported** - This version of Gatsby no longer receives official support of any kind.
+
+## What does this mean for users of the Gatsby framework?
+
+- To receive the newest enhancements and bug fixes, ensure that you've [migrated to Gatsby Version 4](/docs/reference/release-notes/migrating-from-v3-to-v4/) by **January 1, 2022**
+- Continue reporting any issues as you typically would, either using [support](https://www.gatsbyjs.com/support/) on Gatsbyjs.com, or by [opening an issues](https://github.com/gatsbyjs/gatsby/issues/new/choose) in our GitHub repository.
+
+## What does this mean for Gatsby Cloud?
+
+Your Gatsby-powered sites will continue to run as they do today in Gatsby Cloud. However, as enhancements are delivered within Gatsby Cloud and the Gatsby framework, you may need to upgrade your site(s) in order to take advantage of those features and performance enhancements.