From 52c0f0bf0f9ecd0d161673ce5ccfd797db1cdf85 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Fri, 26 Feb 2021 05:52:12 -0800 Subject: [PATCH] doc: revise LTS text in collaborator guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR -> pull request can -> might (to be clear it's about possibility) were -> do for active/passive parallel structure PR-URL: https://github.com/nodejs/node/pull/37527 Reviewed-By: Antoine du Hamel Reviewed-By: Richard Lau Reviewed-By: Michaël Zasso Reviewed-By: Darshan Sen Reviewed-By: Gerhard Stöbich --- doc/guides/collaborator-guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/guides/collaborator-guide.md b/doc/guides/collaborator-guide.md index c596c655118c68..4edc2e16f9cff1 100644 --- a/doc/guides/collaborator-guide.md +++ b/doc/guides/collaborator-guide.md @@ -760,10 +760,10 @@ Each LTS release has a corresponding branch (v10.x, v8.x, etc.). Each also has a corresponding staging branch (v10.x-staging, v8.x-staging, etc.). Commits that land on master are cherry-picked to each staging branch as -appropriate. If a change applies only to the LTS branch, open the PR against the -*staging* branch. Commits from the staging branch land on the LTS branch only -when a release is being prepared. They can land on the LTS branch in a different -order than they were in staging. +appropriate. If a change applies only to the LTS branch, open the pull request +against the *staging* branch. Commits from the staging branch land on the LTS +branch only when a release is being prepared. They might land on the LTS branch +in a different order than they do in staging. Only members of @nodejs/backporters should land commits onto LTS staging branches.