Tighten the rules of what can be merged in patch versions #16890
Conversation
This file contains hidden or 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
tgalopin
reviewed
Jun 17, 2022
tgalopin
reviewed
Jun 17, 2022
ogizanagi
approved these changes
Jun 17, 2022
wouterj
approved these changes
Jun 17, 2022
fabpot
force-pushed
the
maintenance-tweaks
branch
from
ee23673 to
6627a1b
Compare
xabbuh
reviewed
Jun 17, 2022
|
Thank you Fabien. |
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.
Over the years, we've had several patch releases with BC breaks as we tend to merge more than just bug fixes.
In the last few months, we've tried to be more strict. Here is an update to the docs to formalize these changes.