Update release plan

Author: knolleary

about/releases/index.md

@@ -4,30 +4,27 @@ title: Release Plan
 slug: releases
 ---
 
-_Updated: 2021-10-21_
+_Updated: 2022-08-04_
 
 This plan is a guide for how the project plans to schedule upcoming releases, taking
 into account the release schedule of the underlying Node.js runtime.
 
 ![](release-plan.png)
 
 
-The active Node-RED stream (2.x) will get a new minor version release (for example, 2.1 ->  2.2)
-every three months. Maintenance releases (for example 2.1.0 -> 2.1.1) will continue
+The active Node-RED stream (3.x) will get a new minor version release (for example, 3.1 ->  3.2)
+every three months. Maintenance releases (for example 3.1.0 -> 3.1.1) will continue
 to happen as and when they are needed.
 
-At the end of April 2022, when Node 12.x reaches its end-of-life, we will publish
-Node-RED 3.x that will *drop* support for Node 12.
+At the end of April 2023, when Node 14.x reaches its end-of-life, we will publish
+Node-RED 4.x that will *drop* support for Node 14.
 
-The 2.x stream will then enter maintenance mode. It will only receive bug fixes
-and security updates. New features could get back-ported from 3.x if there was
+The 3.x stream will then enter maintenance mode. It will only receive bug fixes
+and security updates. New features could get back-ported from 4.x if there was
 a very good reason to do so as well as people available to do the work.
 
-The 3.x stream will continue in active development with a minor release every
-three months or so until April 2023 when Node 14.x reaches its end-of-life. We
-then publish Node-RED 4.x and the cycle continues. The 2.x stream will reach its
-end-of-life soon after the 4.x release. The exact timing of that will be something
-we will need to discuss further.
+The 4.x stream will continue in active development with a minor release every
+three months or so for a year, when the next major release is made.
 
 This proposal means:
 
@@ -37,13 +34,14 @@ This proposal means:
  - We have a plan that enables us to make potentially breaking changes once a year.
 
 
-Release | Initial     | Maintenance Start    | End-of-life
---------|-------------|----------------------|-----------------
-1.x     | 2019-09-30  | 2021-04-30           | 2022-06-30
-2.x     | 2021-04-30  | 2022-04-30           | 2023-06-30
-3.x     | 2022-04-30  | 2023-04-30           | 2024-06-30
+Release | Initial         | Maintenance Start    | End-of-life
+--------|-----------------|----------------------|-----------------
+1.x     | 2019-09-30      | 2021-04-30           | 2022-06-30
+2.x     | 2021-07-22      | 2022-07-14           | 2023-06-30
+3.x     | 2022-07-14      | *2023-04-30* *       | 2024-06-30
+4.x     | *2023-04-30* *  | *2024-04-30* *       | 2025-06-30
 
-_Dates are subject to change_
+_* Dates are subject to change_
 
 References:
  - [Blog post: Going beyond Node-RED 1.x](https://nodered.org/blog/2020/07/01/release-plans)