From 53a2b97f6bf0de7e9e9a9adb938d5e430f0a2836 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 27 Mar 2019 22:35:43 -0700 Subject: [PATCH 1/3] doc: remove "How is an LTS release cut?" section 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. --- COLLABORATOR_GUIDE.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 09d11eb9691073..9900dac6e1fde6 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -681,13 +681,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 | From bb7949dd875af177569e3dc7324d41d127ba2109 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 28 Mar 2019 06:34:26 -0700 Subject: [PATCH 2/3] fixup! doc: remove "How is an LTS release cut?" section --- COLLABORATOR_GUIDE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 9900dac6e1fde6..2ceb26128357a1 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -34,7 +34,6 @@ - [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. From 64b06480107a24f2316b6361b7a90321fdf084c5 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 28 Mar 2019 06:36:13 -0700 Subject: [PATCH 3/3] fixup! fixup! doc: remove "How is an LTS release cut?" section --- COLLABORATOR_GUIDE.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 2ceb26128357a1..6e85bdc02eef95 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -30,8 +30,6 @@ - [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) * [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker)