From a0db2f2fec28ad163e6fccd0d7a4b7d42aba8ee4 Mon Sep 17 00:00:00 2001 From: Andre Wanlin Date: Thu, 31 Oct 2024 09:46:50 -0500 Subject: [PATCH] Added sentence about release timing Signed-off-by: Andre Wanlin --- docs/overview/versioning-policy.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/overview/versioning-policy.md b/docs/overview/versioning-policy.md index 2ae73e1383..52c6087674 100644 --- a/docs/overview/versioning-policy.md +++ b/docs/overview/versioning-policy.md @@ -166,10 +166,7 @@ following schedule for determining the [Node.js releases](https://nodejs.org/en/ - At any given point in time we support exactly two adjacent even-numbered releases of Node.js, for example v12 and v14. -- Once a new Node.js release becomes _Active LTS_ we switch to support that - release and the previous one. The switch is not immediate but done as soon - as possible. You can find the Node.js version supported by each release - in the `engines` field in the root `package.json` of a new app. +- Once a new Node.js release becomes _Active LTS_ we switch to support that release and the previous one. The switch is not immediate but done as soon as possible. This support will come in the first Backstage main release line release after a Node.js release becomes _Active LTS_. You can find the Node.js version supported by each release in the `engines` field in the root `package.json` of a new app. When we say _Supporting_ a Node.js release, that means the following: