Skip to content

doc: clarify the meaning of legacy status#42269

Merged
nodejs-github-bot merged 11 commits intonodejs:masterfrom
RaisinTen:doc/clarify-the-meaning-of-legacy-status
Mar 14, 2022
Merged

doc: clarify the meaning of legacy status#42269
nodejs-github-bot merged 11 commits intonodejs:masterfrom
RaisinTen:doc/clarify-the-meaning-of-legacy-status

Conversation

@RaisinTen
Copy link
Copy Markdown
Member

@RaisinTen RaisinTen commented Mar 9, 2022

Fixes: #42230
Fixes: #42232

Signed-off-by: Darshan Sen raisinten@gmail.com

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ljharb ljharb ljharb left review comments

@bnb bnb bnb left review comments

@mcollina mcollina mcollina approved these changes

@jasnell jasnell jasnell approved these changes

@Trott Trott Trott approved these changes

@lpinca lpinca lpinca approved these changes

@targos targos targos approved these changes

@tniessen tniessen tniessen approved these changes

@gireeshpunathil gireeshpunathil gireeshpunathil approved these changes

@VoltrexKeyva VoltrexKeyva VoltrexKeyva approved these changes

+2 more reviewers

@isaacs isaacs isaacs left review comments

@Mesteery Mesteery Mesteery approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. doc Issues and PRs related to the documentations.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Are we ready to deprecate url.parse() now? Acceptance of changes made to the legacy APIs