Skip to content

Commit ba81e7c

Browse files
Trotttargos
authored andcommitted
doc: revise LTS text in collaborator guide
PR -> pull request can -> might (to be clear it's about possibility) were -> do for active/passive parallel structure PR-URL: #37527 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de>
1 parent 7529a97 commit ba81e7c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/guides/collaborator-guide.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -760,10 +760,10 @@ Each LTS release has a corresponding branch (v10.x, v8.x, etc.). Each also has a
760760
corresponding staging branch (v10.x-staging, v8.x-staging, etc.).
761761

762762
Commits that land on master are cherry-picked to each staging branch as
763-
appropriate. If a change applies only to the LTS branch, open the PR against the
764-
*staging* branch. Commits from the staging branch land on the LTS branch only
765-
when a release is being prepared. They can land on the LTS branch in a different
766-
order than they were in staging.
763+
appropriate. If a change applies only to the LTS branch, open the pull request
764+
against the *staging* branch. Commits from the staging branch land on the LTS
765+
branch only when a release is being prepared. They might land on the LTS branch
766+
in a different order than they do in staging.
767767

768768
Only members of @nodejs/backporters should land commits onto LTS staging
769769
branches.

0 commit comments

Comments
 (0)