Reorder migrations for v2 minor upgrades #7214
Merged
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
Currently, the order of migrations is: `2.2.2 -> 2.2.5`. `2.0 -> 2.1`, `2.1 -> 2.2` This order is rather confusing, and I would propose to make it follow version numbers either top down, or bottom up. As someone wo is upgrading from 2.0 to 2.2, I can now follow the migrations one by one without checking the whole document, if there are other changes that might be important for the version skips I try to do.
ldez
added
area/documentation
kind/bug/fix
|
Hello @peschmae, Indeed the order is wrong, but in the v2.3 we reorganized those minor migration guides in the following order: 2.0 -> 2.1, 2.1 -> 2.2, 2.2.2 -> 2.2.5 Thanks for your time and interest in Traefik! |
ldez
added
contributor/waiting-for-corrections
and removed
contributor/waiting-for-corrections
labels
|
Hello @peschmae, I made the changes :) Thanks anyway 👍 |
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.
What does this PR do?
This change reorders the migrations for v2 to follow the releases from bottom to top. (Oldest migrations at the bottom, newer ones at the top.)
Motivation
Currently, the order of migrations is:
2.2.2 -> 2.2.5.2.0 -> 2.1,2.1 -> 2.2As someone wo is upgrading from 2.0 to 2.2, I can now follow the migrations one by one without checking the whole document, if there are other changes that might be important for the version skips I try to do.
More