@@ -463,11 +463,11 @@ Runtime Deprecation cycle. However, there is no requirement that deprecated
|
463 | 463 | code must progress ultimately to *End-of-Life*. Documentation-only and runtime |
464 | 464 | deprecations may remain indefinitely. |
465 | 465 | |
466 | | -A best effort will be made to communicate pending deprecations and associated |
467 | | -mitigations with the ecosystem as soon as possible (preferably before the pull |
468 | | -request adding the deprecation lands on the master branch). All deprecations |
469 | | -included in a Node.js release should be listed prominently in the "Notable |
470 | | -Changes" section of the release notes. |
| 466 | +Communicate pending deprecations and associated mitigations with the ecosystem |
| 467 | +as soon as possible (preferably before the pull request adding the deprecation |
| 468 | +lands on the master branch). Use the `notable-change` label on all pull requests |
| 469 | +that add a new deprecation or move an existing deprecation to a new deprecation |
| 470 | +level. |
471 | 471 | |
472 | 472 | ### Involving the TSC |
473 | 473 | |
|