docs: security policy change to only support each active major release #1297
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ive major version.
benhoyt
approved these changes
Jul 22, 2024
dimaqq
approved these changes
Jul 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We strongly encourage charms to use the latest release of ops, and put in a lot of effort to make sure that there are no compatibility issues that would prevent that. As such, rather than promising to do security releases for a year of versions (with our monthly release cadence, this would generally mean 10-12 security releases), only promise to do one for each active major release (so that would be only for 2.x now, and might be 2.x and 3.x at some point in the future).
This is all that we promise, but we could, of course, choose to do more if there was some reason to do so on a case-by-case basis.
This seems to balance the amount of work required to do many small releases and the work that we put into compatibility better than the previous policy.