From f5db5090bce5a165c43c6789b2e958a94cb3146b Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Mon, 28 Jan 2019 17:03:14 -0800 Subject: [PATCH] doc: remove outdated COLLABORATOR_GUIDE sentence about breaking changes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The TSC has delegated authority over LTS and Current branches to the Release WG. Remove the bullet point about TSC having authority to determine that a breaking change is necessary on LTS and Current release branches. Retaining that authority would require de-chartering the Release WG. Fixes: https://github.com/nodejs/TSC/issues/660 PR-URL: https://github.com/nodejs/node/pull/25780 Reviewed-By: Sakthipriyan Vairamani Reviewed-By: Michaël Zasso Reviewed-By: Richard Lau Reviewed-By: Myles Borins --- COLLABORATOR_GUIDE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 25fab70575ad46..acc8538219cf9b 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -282,7 +282,6 @@ providing a Public API in such cases. * Resolving critical security issues. * Fixing a critical bug (e.g. fixing a memory leak) requires a breaking change. - * There is TSC consensus that the change is required. * If a breaking commit does accidentally land in a Current or LTS branch, an attempt to fix the issue will be made before the next release; If no fix is provided then the commit will be reverted.