4.5.3 upgradepath for master branch#824
Conversation
|
LGTM |
There was a problem hiding this comment.
shouldn't we keep this as 452to460 untill 453 is actually released with db migrations? it is not needed otherwise
There was a problem hiding this comment.
I think 4.5.3 would be only a bugfix release that ought not involve any schema change. Since, 4.5.2 to 4.5.3 won't have any schema changes, adding a linear upgrade paths simplifies the paths. IMO, it's just stubs.
f1f12e6 to
b2cf52e
Compare
(cherry picked from commit 17166eb) Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
b2cf52e to
5b5152b
Compare
|
cloudstack-pull-rats #620 SUCCESS |
|
cloudstack-pull-rats #621 SUCCESS |
|
provided we release 4.5.3 before 4.6.0; LGTM |
|
cloudstack-pull-analysis #559 ABORTED |
|
cloudstack-pull-analysis #560 ABORTED |
|
@DaanHoogland I think that will work; and also the stubs would allow 4.5.3 users to upgrade to 4.6.0 provided there is no schema changes between 4.5.2 and 4.5.3 (which is an assumption, of course) |
4.5.3 upgradepath for master branchcc @remibergsma @karuturi * pr/824: schema: add 4.5.3 to 4.6.0 upgrade path stubs schema: add 4.5.2 to 4.5.3 upgrade path stubs Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
|
cloudstack-pull-analysis #592 SUCCESS |
cc @remibergsma @karuturi