chore(docs): update optimize update guides to use correct version #2512
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
akeller
reviewed
Aug 30, 2023
optimize/self-managed/optimize-deployment/migration-update/3.10-to-3.11.md
Outdated
Show resolved
Hide resolved
akeller
reviewed
Aug 30, 2023
| @@ -1892,7 +1892,7 @@ module.exports = { | |||
| { | |||
| "Migration & update": [ | |||
| "self-managed/optimize-deployment/migration-update/instructions", | |||
| "self-managed/optimize-deployment/migration-update/3.10-to-3.11", | |||
| "self-managed/optimize-deployment/migration-update/3.10-to-7.20_8.3", | |||
There was a problem hiding this comment.
Visually, the underscore looks great. Good choice!
akeller
reviewed
Sep 1, 2023
optimize/self-managed/optimize-deployment/migration-update/instructions.md
Show resolved
Hide resolved
akeller
reviewed
Sep 1, 2023
Comment on lines
+11
to
+16
| | Update from | Recommended update path to 7.20/8.3 | | ||
| | ------------ | ----------------------------------------------------------------- | | ||
| | 7.20/8.3 | You are on the latest version. | | ||
| | 3.0 - 3.10.x | Rolling update to 7.20/8.3 | | ||
| | 2.0 - 2.7 | 1. Rolling update to 2.7 <br /> 2. Rolling update from 2.7 to 3.0 | | ||
| | 1.0 - 1.5 | No update possible. Use the latest version directly. | |
There was a problem hiding this comment.
Is this true for the update path to 7.20/8.3? Or are there other changes that need to be made in the migration instruction section to support this or the 3.7 to 7.20/8.3 path?
… into use_optimize_720_83_for_update_guide
|
I can see that optimize 3.11 is also mentioned in |
|
@misiekhardcore let's update it there too. 3.11 won't exist as far as I'm aware. |
misiekhardcore
approved these changes
Sep 6, 2023
|
@misiekhardcore I'll merge this in. When @RomanJRW is back, we can review and iterate to make sure this looks good for the minor release 💪 thank you! |
9 tasks
pepopowitz
pushed a commit
that referenced
this pull request
Oct 16, 2024
) * chore(docs): update optimize update guides to use correct version * Update optimize/self-managed/optimize-deployment/migration-update/3.10-to-3.11.md * more updates for 7.20_8.3 * update update chart * review fixes * replace last 3.11 to 7.20/8.3 --------- Co-authored-by: Amara Graham <[email protected]> Co-authored-by: Amara <[email protected]> Co-authored-by: misiekhardcore <[email protected]> Co-authored-by: Michał Konopski <[email protected]>
9 tasks
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.
Description
In line with the future Optimize versioning, this updates the update notes to use the future versioning system
When should this change go live?
The version changes comes with the next minor release, but earlier docs changes are also fine to help users get used to the new scheme
holdlabel or convert to draft PR)?PR Checklist
/versioned_docsdirectory, or they are not for an already released version./docsdirectory (aka/next/), or they are not for future versions.