modules/understanding-upgrade-channels: Blocked update edges are still supported

[wking]

If we supported them at some point, we will continue to support the edges even if they are no longer recommended.

[netlify]

Deploy preview for osdocs ready!

Built with commit 26e6938

https://deploy-preview-32091--osdocs.netlify.app

[codyhoag]

@jiajliu can you ACK from a QE perspective?

@sferich888 since this is updating some support statements, can you confirm?

[sferich888]

/lgtm

[jeana-redhat]

@sferich888 I'm going to label this with 4.5+ to mark it for cherrypicking into all current and future branches. Let me know if any of those should be omitted.

[sdodson]

@jeana-redhat @codyhoag What's left to move this out? Given that this is all after QE has signed off on releases (we only ship errata after their sign off) I'm not sure they'll be concerned about this change at all.

[jiajliu]

LGTM.

[jeana-redhat]

@sdodson thanks for following up. Looks like we thought we needed QE ack, and now we have it even though as you say it's not required. Only outstanding question as far as I know is confirmation that this goes into all releases (4.5+) - do you know if that's right? If so, I'll review for docs compliance and merge/cherrypick.

[jeana-redhat]

docs review: lgtm

[sdodson]

@jeana-redhat yes, all currently supported versions is fine

[jeana-redhat]

/cherrypick enterprise-4.8

[jeana-redhat]

/cherrypick enterprise-4.7

[jeana-redhat]

/cherrypick enterprise-4.6

[jeana-redhat]

/cherrypick enterprise-4.5

[openshift-cherrypick-robot]

@jeana-redhat: new pull request created: #32814

Details

In response to this:

/cherrypick enterprise-4.8

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/test-infra repository.

[jeana-redhat]

@sdodson ACK and done - tyvm! 👍

[openshift-cherrypick-robot]

@jeana-redhat: #32091 failed to apply on top of branch "enterprise-4.7":

Applying: modules/understanding-upgrade-channels: Blocked update edges are still supported
Using index info to reconstruct a base tree...
M	modules/understanding-upgrade-channels.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/understanding-upgrade-channels.adoc
CONFLICT (content): Merge conflict in modules/understanding-upgrade-channels.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 modules/understanding-upgrade-channels: Blocked update edges are still supported
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.7

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/test-infra repository.

[openshift-cherrypick-robot]

@jeana-redhat: new pull request created: #32815

Details

In response to this:

/cherrypick enterprise-4.6

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/test-infra repository.

[openshift-cherrypick-robot]

@jeana-redhat: new pull request created: #32816

Details

In response to this:

/cherrypick enterprise-4.5

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/test-infra repository.

[jeana-redhat]

/cherrypick enterprise-4.7

[openshift-cherrypick-robot]

@jeana-redhat: #32091 failed to apply on top of branch "enterprise-4.7":

Applying: modules/understanding-upgrade-channels: Blocked update edges are still supported
Using index info to reconstruct a base tree...
M	modules/understanding-upgrade-channels.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/understanding-upgrade-channels.adoc
CONFLICT (content): Merge conflict in modules/understanding-upgrade-channels.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 modules/understanding-upgrade-channels: Blocked update edges are still supported
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.7

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/test-infra repository.