commit 73c71ed95cebd77c3eeaa97ba7582b5c2c354432
parent 35e50d79c630b05f67a840ebe21b4043ba9a6066
Author: Gregory Anders <8965202+gpanders@users.noreply.github.com>
Date: Fri, 15 Sep 2023 09:32:47 -0500
docs(MAINTAIN): Add note about deprecation policy exceptions (#25159)
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
Diffstat:
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/MAINTAIN.md b/MAINTAIN.md
@@ -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
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
- 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
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
------------------------
