What's New process

[gaktive]

Going forward on tickets like https://github.com/rancher/dashboard/issues/4678, once PMs provide us with the content for the What's New section, as part of the review process, we need a way to poke the other engineering managers to validate that the wording is correct.

The two scenarios to consider:

1. the information is accurate
2. if a feature or other documented component is pulled at the last minute, we reflect that information appropriately

[catherineluse]

I think the docs team should do the poking since they are talking to the same people about the release notes as well. When a feature is pulled, they already update the release notes so they can update this doc as well. And adding the final what's new version can be a list item in the release process

[gaktive]

https://github.com/rancher/dashboard/issues/5041 features the work as part of the overall 2.6.4 release as a checklist item from the parent https://github.com/rancher/rancher/issues/36375. I'll work with @Jono-SUSE-Rancher on what he sees from the broader product goals, then figure out if the UI needs its own timelines.

[MKlimuszka]

Does this require QA testing?

[gaktive]

@MKlimuszka For now, there's nothing to test since this more of the process of how UI does the work. I'm going to push this to 2.6.6 since for 2.6.5, we'll just do what's needed for https://github.com/rancher/dashboard/issues/5638.

[gaktive]

For now, the process has been documented internally since it remains ad hoc.

For 2.7.0, PR started - https://github.com/rancher/dashboard/pull/7172 (draft)

[gaktive]

Updated PR based on current feedback. Should be ready for @nwmac shortly.