Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[pull] master from gatsbyjs:master #530

Merged
merged 1 commit into from
Apr 23, 2021
Merged

[pull] master from gatsbyjs:master #530

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Creating a basic landing page to which we can link from our outbound … ( 
gatsbyjs#30988)

Co-authored-by: Megan Sullivan <megan@gatsbyjs.com>
  • Loading branch information
@pragmaticpat @meganesu
pragmaticpat and meganesu committed Apr 23, 2021
commit b1905b1ef36235c6c89fba111f3f87f9c7f39cc4
30 changes: 30 additions & 0 deletions docs/docs/reference/release-notes/v2-maintenance-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
title: Gatsby Framework Version Support
---

## Introduction

As we continue evolving the Gatsby framework, and as we move from one major version to the next, we will communicate the duration and types of support provided to the prior major version. This allows users to effectively plan their Gatsby framework upgrades.

## What is happening, when?

Starting on **June 8, 2021**:

- Gatsby Version 3 will be considered the Active Long-Term Support version of Gatsby.
- This means that users will need to leverage Gatsby Version 3 in order to take advantage of new features and receive bug fixes.
- Gatsby Version 2.32 will enter Maintenance Long-Term Support.
- This means that users of Version 2.32 will only receive critical patches
- The Maintenance Long-Term Support will continue until the release of Gatsby v4 (date TBD).

## What are the characteristics of a "critical patch"?

Critical patches address issues that prevent 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.

## 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 3](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/) by **June 8, 2021**
- 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.