BZ1918456 new changes

[StephenJamesSmith]

@wking @[email protected] - Plz verify/approve (lgtm).

[netlify]

Deploy preview for osdocs ready!

Built with commit 9a2a56f

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

[vikram-redhat]

@kenyis - PTAL.

[vikram-redhat]

@wking @sferich888 @kenyis @StephenJamesSmith - not sure who can answer this, but we recently added this release note entry via an exception process (#29835).

I am trying to figure out why this entry needs to change so soon after that. Was something missed in the original explanations? Is there someone whose ack we should have taken before publishing it that we didn't?

Changing release notes in between releases does require us to notify stakeholders and get acks, and I would like to reduce the paperwork involved.

[wking]

I thought this was going to be:

Customers who are using the kernel-rt and run either {product-title} 4.6 or 4.7.0 will experience a severe impact.

My point is that both folks running 4.6 and 4.7 are already impacted, so this bug has nothing to do with upgrades to 4.7. It might have something to do with updates from 4.5 to 4.6, but that's irrelevant for the 4.7-and-later release notes.

[StephenJamesSmith]

wking didn't have a chance to review during the initial iteration and had some important changes. Sorry about the inconvenience.

[StephenJamesSmith]

@wking Above change has been made.

[wking]

/lgtm

[wking]

Is there someone whose ack we should have taken before publishing it that we didn't?

Not me personally, but the updates team (which should be more similar to @openshift/openshift-team-cincinnati , I'll run down the difference) would like to review statements about OCP update recommendations. Because if an update is really not recommended, we want to stop recommending that update edge. We want to minimize divergence between human-oriented docs and the Cincinnati API that represents OCP update recommendations.

[wking]

Anything we can do to help this along?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.