engine/schema: Use same upgrade path as 4.15.1-4.16.0 as for 4.15.2#5385
Merged
yadvr merged 1 commit intoapache:mainfrom Aug 31, 2021
Merged
engine/schema: Use same upgrade path as 4.15.1-4.16.0 as for 4.15.2#5385yadvr merged 1 commit intoapache:mainfrom
yadvr merged 1 commit intoapache:mainfrom
Conversation
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
yadvr
requested review from
davidjumani,
nvazquez,
shwstppr,
sureshanaparti and
weizhouapache
yadvr
commented
Aug 27, 2021
| .next("4.14.1.0", new Upgrade41400to41500()) | ||
| .next("4.15.0.0", new Upgrade41500to41510()) | ||
| .next("4.15.1.0", new Upgrade41510to41600()) | ||
| .next("4.15.2.0", new Upgrade41510to41600()) |
Member
Author
There was a problem hiding this comment.
this is same pattern we used in 4.14.0/4.14.1...
Member
Author
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1039 |
DaanHoogland
approved these changes
Aug 27, 2021
Contributor
|
we'll have to manually test this by upgrading a snapshot 4.15 install to 4.16 |
Member
Author
|
Simple test is to use mvn deploy db on 4.15 branch, register fake template and then build and run mgmt server on main branch. Upgrade tests will thoroughly happen on 4.15 so let's merge this first? |
Member
Author
|
Did a manual test, the upgrade seems to kick in. I'm merging this on discretion as upgrade tests are done as part of release/pre-RC efforts. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Introduce same Db upgrade path from both 4.15.1/4.15.2 to 4.16.0