Qual: "Backport phan to 18.0" Prepare 20.0 branch #30615
Closed
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
mdeweerd
force-pushed
the
backport/phan/20
branch
from
1378cfb
to
9904b9e
Compare
mdeweerd
changed the title
mdeweerd
changed the title
|
Old versions are versions already released and open for bug fix and only bug fix maintenance, as we must reduce as much as possible the printing of any change on maintenance versions. So code quality on already released version is not necessary so we can be more focused on develop branch. |
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.
Qual: "Backport phan to 18.0" Prepare 20.0 branch
The goal is integration in 18.0 and 19.0 as phan is already setup in 20.0, but this PR is to make it "seamless" to
It must be merged after the "empty" PR to develop which needs to be integrated first.
By following that order, the upward path (from 18.0 to 19.0 to 20.0 to develop) should be flawless, without any merge issues for the changes related to phan.
However, do not make a squash merge to make sure the history is understood by git.