Skip to content

Commit a545cfe

Browse files
Trotttargos
authored andcommitted
doc: edit "How Can I Help?" in Collaborator Guide
Edit the "How Can I Help?" section of the Collaborator Guide to keep sentences simple, short, and direct. PR-URL: #26895 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
1 parent 92b666a commit a545cfe

File tree

1 file changed

+21
-27
lines changed

1 file changed

+21
-27
lines changed

COLLABORATOR_GUIDE.md

+21-27
Original file line numberDiff line numberDiff line change
@@ -659,33 +659,27 @@ branches.
659659

660660
#### How can I help?
661661

662-
When you send your pull request, please include information about whether your
663-
change is breaking. If you think your patch can be backported, please include
664-
that information in the PR thread or your PR description. For more information
665-
on backporting, please see the [backporting guide][].
666-
667-
Several LTS related issue and PR labels have been provided:
668-
669-
* `lts-watch-v10.x` - tells the LTS WG that the issue/PR needs to be
670-
considered for landing in the `v10.x-staging` branch.
671-
* `lts-watch-v8.x` - tells the LTS WG that the issue/PR needs to be
672-
considered for landing in the `v8.x-staging` branch.
673-
* `lts-watch-v6.x` - tells the LTS WG that the issue/PR needs to be
674-
considered for landing in the `v6.x-staging` branch.
675-
* `land-on-v10.x` - tells the release team that the commit should be landed
676-
in a future v10.x release.
677-
* `land-on-v8.x` - tells the release team that the commit should be landed
678-
in a future v8.x release.
679-
* `land-on-v6.x` - tells the release team that the commit should be landed
680-
in a future v6.x release.
681-
682-
Any Collaborator can attach these labels to any PR/issue. As commits are
683-
landed into the staging branches, the `lts-watch-` label will be removed.
684-
Likewise, as commits are landed in a LTS release, the `land-on-` label will
685-
be removed.
686-
687-
Collaborators are encouraged to help the LTS WG by attaching the appropriate
688-
`lts-watch-` label to any PR that may impact an LTS release.
662+
When you send your pull request, please state if your change is breaking. Also
663+
state if you think your patch is a good candidate for backporting. For more
664+
information on backporting, please see the [backporting guide][].
665+
666+
There are several LTS-related labels:
667+
668+
* `lts-watch-` labels are for pull requests to consider for landing in staging
669+
branches. For example, `lts-watch-v10.x` would be for a change
670+
to consider for the `v10.x-staging` branch.
671+
672+
* `land-on-` are for pull requests that should land in a future v*.x
673+
release. For example, `land-on-v10.x` would be for a change to land in Node.js
674+
10.x.
675+
676+
Any Collaborator can attach these labels to any pull request/issue. As commits
677+
land on the staging branches, the backporter removes the `lts-watch-` label.
678+
Likewise, as commits land in an LTS release, the releaser removes the `land-on-`
679+
label.
680+
681+
Attach the appropriate `lts-watch-` label to any PR that may impact an LTS
682+
release.
689683

690684
#### How is an LTS release cut?
691685

0 commit comments

Comments
 (0)