diff options
| author | Gregory Anders <8965202+gpanders@users.noreply.github.com> | 2023-09-15 09:32:47 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-09-15 09:32:47 -0500 |
| commit | 73c71ed95cebd77c3eeaa97ba7582b5c2c354432 (patch) | |
| tree | 8912923fdaaab1f248e87936b56e7ce26dd96cd7 | |
| parent | 35e50d79c630b05f67a840ebe21b4043ba9a6066 (diff) | |
| download | rneovim-73c71ed95cebd77c3eeaa97ba7582b5c2c354432.tar.gz rneovim-73c71ed95cebd77c3eeaa97ba7582b5c2c354432.tar.bz2 rneovim-73c71ed95cebd77c3eeaa97ba7582b5c2c354432.zip | |
docs(MAINTAIN): Add note about deprecation policy exceptions (#25159)
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
| -rw-r--r-- | MAINTAIN.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/MAINTAIN.md b/MAINTAIN.md index f3fe873a84..3e31fde118 100644 --- 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 ------------------------ |