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
docs: update the version specific notes table #16710
Merged
joestringer
merged 1 commit into
cilium:master
from
bmcustodio:bruno-upgrade-vsn-update
Jun 30, 2021
Merged
docs: update the version specific notes table #16710
joestringer
merged 1 commit into
cilium:master
from
bmcustodio:bruno-upgrade-vsn-update
Jun 30, 2021
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
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Jun 30, 2021
bmcustodio
added
area/documentation
Impacts the documentation, including textual changes, sphinx, or other doc generation code.
backport-pending/1.9
labels
Jun 30, 2021
qmonnet
approved these changes
Jun 30, 2021
Updates the table in the "Version Specific Notes" subsection of the "Upgrade" page in order to be explicit about the supported upgrade paths. Signed-off-by: Bruno Miguel Custódio <brunomcustodio@gmail.com>
qmonnet
approved these changes
Jun 30, 2021
qmonnet
added
the
release-note/misc
This PR makes changes that have no direct user impact.
label
Jun 30, 2021
maintainer-s-little-helper
bot
removed
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Jun 30, 2021
qmonnet
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jun 30, 2021
joestringer
approved these changes
Jun 30, 2021
This was referenced Jul 1, 2021
joestringer
moved this from Backport pending to v1.10
to Needs backport from master
in 1.10.4
Jul 19, 2021
@bmcustodio I have set this back to "needs-backport/1.10" since it seems like the backport to that branch was not yet performed. This will allow the regular backporters to pick up this PR and backport it. In future if you start then abandon a backport, then please consider updating the labels like this too, as it helps track & ensure we get the patches lined up correctly on each of the branches. |
joestringer
moved this from Backport pending to v1.10
to Backport done to v1.10
in 1.10.5
Oct 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/documentation
Impacts the documentation, including textual changes, sphinx, or other doc generation code.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
Updates the table in the "Version Specific Notes" subsection of the "Upgrade" page in order to be explicit about the supported upgrade paths.