docs: Update version tags after v0.12.0 release #502
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
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: israel-hdez The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
oss-prow-bot
bot
requested review from
ckadner,
joerunde,
rafvasq and
tjohnson31415
Signed-off-by: Edgar Hernández <[email protected]>
Signed-off-by: Christian Kadner <[email protected]>
israel-hdez
force-pushed
the
update-version-refs-012
branch
from
1c276f8
to
067be24
Compare
Signed-off-by: Edgar Hernández <[email protected]>
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.
Motivation
Doc updates post v0.12.0 release.
Modifications
Update the following files in the
mainbranch, replacing all occurrencespointing to the old
release-*branch or the previous release version tag(e.g.
v0.11.0) with the new release branch name or new version tags.Submit them in a PR to
main, and wait for that PR to be merged:docs/install/install-script.mddocs/component-versions.mddocs/quickstart.mdscripts/setup_user_namespaces.shResult
Docs will warn users to use docs of latest release, rather than
maindocs.