From 22529cfd8c31439dbcd7d81b14dd482f7d55b6ae Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Tue, 12 Jun 2018 21:14:15 -0700 Subject: [PATCH] doc: make Deprecation cycle explanation more brief The Deprecation cycle explanation in the COLLABORATOR_GUIDE.md file is now more concise. --- COLLABORATOR_GUIDE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index 99e8b701c69c76..8b7eafa9d2f041 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -453,10 +453,10 @@ the documentation for the assigned deprecation identifier must remain in the Node.js API documentation. -A _Deprecation cycle_ is one full Node.js major release during which an API -has been in one of the three Deprecation levels. (Note that Documentation-Only -Deprecations may land in a Node.js minor release but must not be upgraded to -a Runtime Deprecation until the next major release.) +A _Deprecation cycle_ is a major release during which an API has been in one of +the three Deprecation levels. Documentation-Only Deprecations may land in a +minor release but must not be upgraded to a Runtime Deprecation until the next +major release. No API can be moved to End-of-life without first having gone through a Runtime Deprecation cycle. However, there is no requirement that deprecated