Skip to content

Commit

Permalink
Update release plan
Browse files Browse the repository at this point in the history
  • Loading branch information
knolleary committed Mar 1, 2024
1 parent 32b9566 commit 48023fc
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 27 deletions.
31 changes: 14 additions & 17 deletions about/releases/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,27 +4,24 @@ title: Release Plan
slug: releases
---

_Updated: 2022-08-04_
_Updated: 2024-01-03_

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 project aims to make a new major release around April each year. This aligns
with when versions of Node.js reach their end-of-life and enables us to drop support
for them.

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.
The active Node-RED stream will get regular minor releases (for example 4.0 -> 4.1)
containing new features as well as maintenance releases (for example 4.0.1 -> 4.0.2)
as and when they are needed.

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 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 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.
When a new major version is released, the previous version enters maintenance mode
for an extended period of time. During this time it will only receive bug fixes
and security updates.

This proposal means:

Expand All @@ -36,12 +33,12 @@ This proposal means:

Release | Initial | Maintenance Start | End-of-life
--------|-----------------|----------------------|-----------------
1.x | 2019-09-30 | 2021-04-30 | 2022-06-30
4.x | *2024-04-30* * | *2025-04-30* * | 2026-06-30
3.x | 2022-07-14 | *2024-04-30* * | 2025-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
1.x | 2019-09-30 | 2021-04-30 | 2022-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)
Expand Down
Binary file modified about/releases/release-plan.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
19 changes: 9 additions & 10 deletions docs/faq/node-versions.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,22 @@ title: Supported Node versions
slug: node versions
---

Node-RED currently recommends **Node 18.x or Node 20.x**.
_Updated: 2024-01-03_

Version | Support Level | Notes
-----------|-----------------|------
**20.x** | **Recommended** |
**18.x** | **Recommended** |
16.x | *Supported* |
14.x | *Supported* | Node-RED 3.x or earlier only
12.x | *Supported* | Node-RED 2.x or earlier only
< 10.x | *Unsupported* | Node-RED 1.x or earlier only
Node-RED currently recommends **Node 20.x**.

We try to stay up to date with Node.js releases. Our goal is to support
the [Maintenance and Active LTS releases](https://nodejs.org/en/about/releases/).

We do not generally recommend using the odd numbered Node.js versions - we do not
We do not recommend using the odd numbered Node.js versions - we do not
routinely test against them.

Node-RED Version | Minimum Node.js Version
---|---
4.x | 18
3.x | 14
2.x | 12

With such a large community of 3rd party nodes available to install, we cannot
provide any guarantees on what they support. We rely on the community to keep
up to date.
Expand Down

0 comments on commit 48023fc

Please sign in to comment.