From 28efecccd50a077721f6ce819f1900c9dc19fef8 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 27 Mar 2019 22:35:43 -0700 Subject: [PATCH] doc: remove "How is an LTS release cut?" section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The release process is in the Release plan, linked earlier in the doc. Don't include information here because duplicated information is likely to drift apart, resulting in contradictions and a lack of clarity about which document is correct. (I think the text removed is already out-of-date. I could be wrong, and it doesn't much matter, as it should be removed anyway.) It's also not entirely clear what the utility/relevance of this information is in this particular document. PR-URL: https://github.com/nodejs/node/pull/26955 Reviewed-By: Michaël Zasso Reviewed-By: Ruben Bridgewater Reviewed-By: Anatoli Papirovski Reviewed-By: Luigi Pinca Signed-off-by: Beth Griggs --- COLLABORATOR_GUIDE.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 09d11eb9691073..6e85bdc02eef95 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -30,11 +30,8 @@ - [I Made a Mistake](#i-made-a-mistake) - [Long Term Support](#long-term-support) - [What is LTS?](#what-is-lts) - - [How does LTS work?](#how-does-lts-work) - - [Landing semver-minor commits in LTS](#landing-semver-minor-commits-in-lts) - [How are LTS Branches Managed?](#how-are-lts-branches-managed) - [How can I help?](#how-can-i-help) - - [How is an LTS release cut?](#how-is-an-lts-release-cut) * [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker) This document explains how Collaborators manage the Node.js project. @@ -681,13 +678,6 @@ label. Attach the appropriate `lts-watch-` label to any PR that may impact an LTS release. -#### How is an LTS release cut? - -When the LTS working group determines that a new LTS release is required, -selected commits will be picked from the staging branch to be included in the -release. This process of making a release will be a collaboration between the -LTS working group and the Release team. - ## Who to CC in the issue tracker | Subsystem | Maintainers |