CASMINST-7138: Update CSM 1.3 upgrade prep links; add CSM 1.4 upgrade prep #5683
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
mharding-hpe
requested review from
rustydb,
haroldlongley,
nrockershousen,
spillerc-hpe,
GunashekarKM,
SavioJoshua,
sfkramer,
brookshire,
kkelling-hpe and
don-bahls-hpe
This was referenced Jan 22, 2025
rustydb
approved these changes
Jan 22, 2025
mtupitsyn
approved these changes
Jan 22, 2025
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.
The prepare_for_upgrade.md procedure is only followed when upgrading from the previous CSM version to the current one. The problem is, it mostly contains links into the current CSM version, and this can cause problems. It makes more sense for us to have a "prepare for upgrade to the NEXT csm version" in the current CSM version docs. That way the links can and should be into the same release. And we can have a simple link from the next release docs back to that single page, to limit the connections between the doc versions.
I decided only to do this as far back as CSM 1.3. So this PR is a little different from the ones that will come for 1.4+. This one instead has its "prepare for upgrade" page updated so that its links point into the CSM 1.2 docs directly.
The "new"
upgrade/Prepare_for_Upgrade_to_Next_CSM_Major_Version.mdpage is essentially just theprepare_for_upgradepage from the 1.4 branch, The 1.4 PR updates those docs to point back to that page."Backports":
1.4: #5684
1.5: #5685
1.6: #5686
1.7: #5687