-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[bwc] Add bugfix3 project #126880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bwc] Add bugfix3 project #126880
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
How about removing the 7.17 from
From the BwC tests I believe it makes sense because we do not test the compatibility for upgrades between 7 and 9. I am not sure what might be the other side-effects of removing 7.17 from |
Alternatively, it would be possible to filter the // Now handle all the feature freeze branches
List<String> featureFreezeBranches = developmentBranches.stream()
.filter(b -> Pattern.matches("[0-9]+\\.[0-9]+", b))
.filter(b -> currentVersion.getMajor() - Version.fromString(b, Version.Mode.RELAXED).getMajor() <= 1) // I've added this line
.sorted(reverseOrder(comparing(s -> Version.fromString(s, Version.Mode.RELAXED))))
.toList(); It gives the same result as removing 7.17 from
It also have no side-effects and should be compatible with other branches so we can backport it to 8.x branches. EDIT: |
I didn't managed to make the second solution to pass all the tests yet, so it may be worth to merge this one to unblock the release. |
#126962) * Temporarily bypass competitive iteration for filters aggregation (#126956) * Bump versions after 9.0.0 release * fix merge conflict * Remove 8.16 from branches.json * Bring version-bump related changes from main * [bwc] Add bugfix3 project (#126880) * Sync version bump changes from main again --------- Co-authored-by: Benjamin Trent <ben.w.trent@gmail.com> Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co> Co-authored-by: elasticsearchmachine <58790826+elasticsearchmachine@users.noreply.github.com> Co-authored-by: Brian Seeders <brian.seeders@elastic.co>
There are now 3 "bugfix" projects from a BWC standpoint, which causes the following error:
Because there are two
bugfix2
projects. This adds a 3rd one. I'm not sure if this is the best approach here.Finalizing the
8.18.0
release is blocked until this is solved.