-
Notifications
You must be signed in to change notification settings - Fork 329
Move upgrade_3_0.md file to archives_upgrades folder #995
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
Move upgrade_3_0.md file to archives_upgrades folder #995
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ronaldngounou 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 |
|
Hi @ronaldngounou. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you delete this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dwelsch-esi stated in the issue description that
The "Upgrading etcd clusters and applications" page seems redundant. The "Upgrading" link could goes straight to the main upgrade page, which contains the same information. There's no need to ever visit the Upgrading etcd clusters and applications page.
That's why I deleted that page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aha.
|
/retest |
|
We can ignore the linter failure since it's all content for the 3.0 page. However, I can't merge it until Netlify deploy succeeds, and it's not saying why it's failing. It may not even be related to your changes. |
|
/retest |
|
The deployment is failing because |
0a963d7 to
b5635cb
Compare
d201ded to
ea0a2d2
Compare
|
/ok-to-test |
This commit updates the link in the upgrade_3_1.md file to point to the archives upgrade page instead of the main upgrade page. This change ensures that users are directed to the correct page. Signed-off-by: Ronald Ngounou <[email protected]>
9f1dcd2 to
eea0c34
Compare
Signed-off-by: jasonnwu <[email protected]>
|
You didn't actually need to fix the markdown issues with the 3.0 upgrade file ;-) However: the move to the archives folder doesn't make any difference for anyone reading the documentation. Take a look at the preview; it still looks the same. This brings up the question of, what are we trying to do with the file move? It doesn't break anything, but it doesn't do anything either. If we want to have some upgrades be "older version upgrades", then we'd need to put an |
|
So, I'm looking at #773, and what Dave is talking about has nothing to do with folders. What Dave is asking for is some useful documentation on how to upgrade, in general, in the main It would also be useful to mark out the upgrade steps that have not been recently tested, which is anything before 3.4. All of this would be done in the |
This reverts commit eea0c34.
Signed-off-by: Ronald Ngounou <[email protected]>
…arch-2 Disable exclude_search in _index.md (3.6)
…gate_error Fix the issue of incorrect description of "operations." in the TxnModeWriteWithSharedBuffer function
Signed-off-by: Wendy Ha <[email protected]>
Signed-off-by: Wendy Ha <[email protected]>
Signed-off-by: Wendy Ha <[email protected]>
Signed-off-by: Wendy Ha <[email protected]>
Signed-off-by: Wendy Ha <[email protected]>
Signed-off-by: beifengtz <[email protected]>
Signed-off-by: beifengtz <[email protected]>
Signed-off-by: beifengtz <[email protected]>
Signed-off-by: beifengtz <[email protected]>
Bumps [hugo-extended](https://github.com/jakejarvis/hugo-extended) from 0.147.5 to 0.147.8. - [Commits](jakejarvis/hugo-extended@v0.147.5...v0.147.8) --- updated-dependencies: - dependency-name: hugo-extended dependency-version: 0.147.8 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Add etcd-workbench link to tools
…hugo-extended-0.147.8 Bump hugo-extended from 0.147.5 to 0.147.8
Updates the requirements on [docsy](https://github.com/google/docsy) to permit the latest version. - [Release notes](https://github.com/google/docsy/releases) - [Commits](https://github.com/google/docsy/commits/ace4e37ceedcec9c48d329adb1128201061ef23d) --- updated-dependencies: - dependency-name: docsy dependency-version: ace4e37ceedcec9c48d329adb1128201061ef23d dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
…docsy-0.12.0 Update docsy requirement from 0.11.0 to 0.12.0
Co-authored-by: Josh Berkus <[email protected]>
Co-authored-by: Josh Berkus <[email protected]>
…al-how-to-transactional-write Revise website tutorial how-to-transactional-write
…rt2_clean Recursively copy the contents of v3.6 to v3.7
This commit updates the link in the upgrade_3_1.md file to point to the archives upgrade page instead of the main upgrade page. This change ensures that users are directed to the correct page. Signed-off-by: Ronald Ngounou <[email protected]>
This reverts commit eea0c34.
Signed-off-by: Ronald Ngounou <[email protected]>
This commit updates the link in the upgrade_3_1.md file to point to the archives upgrade page instead of the main upgrade page. This change ensures that users are directed to the correct page. Signed-off-by: Ronald Ngounou <[email protected]>
This reverts commit eea0c34.
…hub.com/ronaldngounou/etcd-io-website into issue773-upgrade-etcd-clusters-app-page
|
Ooof, that did not go well. Here's my recommendation:
|
Overview
This PR aims to fix partially the issue #773.
My contributions:
upgrade_3_0.mdto that folder.A second task related to this issue that this PR is not solving yet is to list document which upgrade paths are supported, recommended, deprecated, and unsupported at the top of the "Upgrading" main page.
I would suggest adding these versions in the list as I am waiting for approval.
recommended: [3.5.21]deprecated: [3.1, 3.2, 3.3, 3.4]unsupported: [2.3 to 3.0]Testing
npm run serve