Skip to content

doc: revise breaking changes material in COLLABORATOR_GUIDE - #25730

Closed
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:revise-moar
Closed

doc: revise breaking changes material in COLLABORATOR_GUIDE#25730
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:revise-moar

Conversation

@Trott

Copy link
Copy Markdown
Member
  • Remove unnecessary paragraph explaining why Current and LTS have
    stability guarantees that master branch does not. (Leave material
    explaining what those stability guarantees are.)
  • Upgrade advisory and passive "Collaborators should take significant
    care" to more direct "Take significant care".
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-botnodejs-github-bot added the doc Issues and PRs related to the documentations. label Jan 27, 2019
@TrottTrott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jan 27, 2019

@mhdawsonmhdawson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Trott

Copy link
Copy Markdown
MemberAuthor

Landed in aa8fcee

@TrottTrott closed this Jan 29, 2019
Trott added a commit to Trott/io.js that referenced this pull request Jan 29, 2019
* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
PR-URL: nodejs#25730
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
targos pushed a commit that referenced this pull request Jan 29, 2019
* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
PR-URL: #25730
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
@targostargos mentioned this pull request Jan 29, 2019
BethGriggs pushed a commit that referenced this pull request Apr 29, 2019
* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
PR-URL: #25730
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
@BethGriggsBethGriggs mentioned this pull request May 1, 2019
BethGriggs pushed a commit that referenced this pull request May 10, 2019
* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
PR-URL: #25730
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
MylesBorins pushed a commit that referenced this pull request May 16, 2019
* Remove unnecessary paragraph explaining why Current and LTS have
stability guarantees that master branch does not. (Leave material
explaining what those stability guarantees are.)
* Upgrade advisory and passive "Collaborators should take significant
care" to more direct "Take significant care".
PR-URL: #25730
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
@Trott
Trott deleted the revise-moar branch January 13, 2022 22:51
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@Trott@nodejs-github-bot@jasnell@antsmartian@BethGriggs@mhdawson