docs(MAINTAIN): Add note about deprecation policy exceptions (#25159)

Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
This commit is contained in:
Gregory Anders 2023-09-15 09:32:47 -05:00 committed by GitHub
parent 35e50d79c6
commit 73c71ed95c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -69,7 +69,7 @@ remove existing features, or refactor parts of the code that would change
user's workflow. In these cases, a deprecation policy is needed to properly user's workflow. In these cases, a deprecation policy is needed to properly
inform users of the change. inform users of the change.
In general, when a feature is slated to be removed it should: When a (non-experimental) feature is slated to be removed it should:
1. Be _soft_ deprecated in the _next_ release 1. Be _soft_ deprecated in the _next_ release
- Use of the deprecated feature will still work. - Use of the deprecated feature will still work.
@ -106,6 +106,10 @@ Feature removals which may benefit from community input or further discussion
should also have a tracking issue (which should be linked to in the release should also have a tracking issue (which should be linked to in the release
notes). notes).
Exceptions to this policy may be made (for experimental subsystems or when
there is broad consensus among maintainers). The rationale for the exception
should be stated explicitly and publicly.
Third-party dependencies Third-party dependencies
------------------------ ------------------------