OCPBUGS-44663: modules/understanding-update-channels: Drop obsolete "up to a day" #86088
Conversation
The text was originally from 1c199f1 (Mod channel doc, 2020-03-20, openshift#19088). When it landed, the file also included 42c1006 (Move KB article "OpenShift 4.2 Upgrades phased roll out" contents into docs, 2020-02-07, openshift#18944)'s "can range from several hours to a day" in the stable-* channel section. 3e702f1 (Remove timeline text, 2020-06-10, openshift#22816) later removed the "several hours to a day" from the stable-* channel section. a8d3109 (Focus the description of the channels only on what goes into the channels, 2022-12-05, openshift#47333) added the "Choosing the correct channel for your cluster" section, with its "generally ... within a week or two", but missed removing the "up to a day" I'm removing now. a8d3109 added: Since the time required to obtain a significant number of data points varies based on many factors, Service LeveL Objective (SLO) is not offered for the delay duration between fast and stable channels. For more information, please see "Choosing the correct channel for your cluster" This commit follows the example set by 3e702f1 and the lack-of-SLO described in a8d3109 by removing the duration text from the channel-changing section.
openshift-ci-robot
added
jira/valid-reference
|
@wking: This pull request references Jira Issue OCPBUGS-44663, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/XS
|
/jira refresh |
openshift-ci-robot
added
the
jira/valid-bug
|
@wking: This pull request references Jira Issue OCPBUGS-44663, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
removed
the
jira/invalid-bug
|
🤖 Tue Dec 10 23:35:51 - Prow CI generated the docs preview: |
|
@wking: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@wking: This pull request references Jira Issue OCPBUGS-44663, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
| @@ -130,5 +130,5 @@ Changing your channel might impact the supportability of your cluster. The follo | |||
|
|
|||
| * You can switch from the `candidate-{product-version}` channel to the `fast-{product-version}` channel if your current release is a general availability release. | |||
|
|
|||
| * You can always switch from the `fast-{product-version}` channel to the `stable-{product-version}` channel. There is a possible delay of up to a day for the release to be promoted to `stable-{product-version}` if the current release was recently promoted. | |||
| * You can always switch from the `fast-{product-version}` channel to the `stable-{product-version}` channel. There is a possible delay for the release to be promoted to `stable-{product-version}` if the current release was recently promoted. | |||
There was a problem hiding this comment.
Small nit:
- You can always switch from the
fast-{product-version}channel to thestable-{product-version}channel. If you recently promoted the current release, the promotion tostable-{product-version}might be delayed.
There was a problem hiding this comment.
Do we know what "recent" means in this context?
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
The text was originally from 1c199f1 (#19088). When it landed, the file also included 42c1006 (#18944)'s "can range from several hours to a day" in the
stable-*channel section. 3e702f1 (#22816) later removed the "several hours to a day" from thestable-*channel section.a8d3109 (#47333) added the "Choosing the correct channel for your cluster" section, with its "generally ... within a week or two", but missed removing the "up to a day" I'm removing now. a8d3109 added:
This commit follows the example set by 3e702f1 and the lack-of-SLO described in a8d3109 by removing the duration text from the channel-changing section.
Version(s): 4.12 through main. Not worth patching older, end-of-life releases. Possibly not even worth patching 4.12?
Issue: https://issues.redhat.com/browse/OCPBUGS-44663
Link to docs preview: https://86088--ocpdocs-pr.netlify.app/openshift-enterprise/latest/updating/understanding_updates/understanding-update-channels-release.html#switching-between-channels_understanding-update-channels-releases
QE review: