doc: use imperative in COLLABORATOR_GUIDE

Instead of wording the paragraph about communicating deprecations with the ecosystem as if it were directed at the ecosystem, write it as in imperative directed at the collaborator, since that is the audience for the COLLABORATOR_GUIDE. Instead of assuring the reader that a best effort will be made, instruct the reader to make the effort to communicate with the ecosystem. PR-URL: #21340 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
nodejs · Jun 15, 2018 · 318d6831bf569e34c4926548804dc0e4e9ceeaa8 · 318d683
1 parent 177a7c0
commit 318d6831bf569e34c4926548804dc0e4e9ceeaa8
Unified Split

Showing with 5 additions and 5 deletions.

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