diff options
| author | Rich Trott <rtrott@gmail.com> | 2019-03-24 15:56:53 -0700 |
|---|---|---|
| committer | Rich Trott <rtrott@gmail.com> | 2019-03-26 16:19:27 -0700 |
| commit | 6342af7ebdd6cd516507fba5a91ffc6878ef7cfb (patch) | |
| tree | 0d50a806d306e316685cf5b60f4a3be98d7bf5b6 /COLLABORATOR_GUIDE.md | |
| parent | 6df9f84f61cd794f017a11606d7e6e4ba638783b (diff) | |
| download | android-node-v8-6342af7ebdd6cd516507fba5a91ffc6878ef7cfb.tar.gz android-node-v8-6342af7ebdd6cd516507fba5a91ffc6878ef7cfb.tar.bz2 android-node-v8-6342af7ebdd6cd516507fba5a91ffc6878ef7cfb.zip | |
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: https://github.com/nodejs/node/pull/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>
Diffstat (limited to 'COLLABORATOR_GUIDE.md')
| -rw-r--r-- | COLLABORATOR_GUIDE.md | 48 |
1 files changed, 21 insertions, 27 deletions
diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 6be5ceda12..09d11eb969 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -659,33 +659,27 @@ branches. #### How can I help? -When you send your pull request, please include information about whether your -change is breaking. If you think your patch can be backported, please include -that information in the PR thread or your PR description. For more information -on backporting, please see the [backporting guide][]. - -Several LTS related issue and PR labels have been provided: - -* `lts-watch-v10.x` - tells the LTS WG that the issue/PR needs to be - considered for landing in the `v10.x-staging` branch. -* `lts-watch-v8.x` - tells the LTS WG that the issue/PR needs to be - considered for landing in the `v8.x-staging` branch. -* `lts-watch-v6.x` - tells the LTS WG that the issue/PR needs to be - considered for landing in the `v6.x-staging` branch. -* `land-on-v10.x` - tells the release team that the commit should be landed - in a future v10.x release. -* `land-on-v8.x` - tells the release team that the commit should be landed - in a future v8.x release. -* `land-on-v6.x` - tells the release team that the commit should be landed - in a future v6.x release. - -Any Collaborator can attach these labels to any PR/issue. As commits are -landed into the staging branches, the `lts-watch-` label will be removed. -Likewise, as commits are landed in a LTS release, the `land-on-` label will -be removed. - -Collaborators are encouraged to help the LTS WG by attaching the appropriate -`lts-watch-` label to any PR that may impact an LTS release. +When you send your pull request, please state if your change is breaking. Also +state if you think your patch is a good candidate for backporting. For more +information on backporting, please see the [backporting guide][]. + +There are several LTS-related labels: + +* `lts-watch-` labels are for pull requests to consider for landing in staging + branches. For example, `lts-watch-v10.x` would be for a change + to consider for the `v10.x-staging` branch. + +* `land-on-` are for pull requests that should land in a future v*.x + release. For example, `land-on-v10.x` would be for a change to land in Node.js + 10.x. + +Any Collaborator can attach these labels to any pull request/issue. As commits +land on the staging branches, the backporter removes the `lts-watch-` label. +Likewise, as commits land in an LTS release, the releaser removes the `land-on-` +label. + +Attach the appropriate `lts-watch-` label to any PR that may impact an LTS +release. #### How is an LTS release cut? |