docs: qualifier

[v1v]

Motivation/summary

update docs after the recent changes from #15350

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[rubvs]

If this is only something to consider for MAJOR, maybe we should put it under the Major Release header?

[v1v]

If this is only something to consider for MAJOR, maybe we should put it under the Major Release header?

I don't know, the qualifier is release agnostic but we used it only for MAJOR releases.

[rubvs]

In that case, I'd still prefer it under Major Release, since that is the only case when we should consider taking it into account. cc @carsonip for an extra take on this. We can always move it out, when we end up using it for non-majors.

[v1v]

That's still part of the Between feature freeze and release section, regardless of the type of release.

[carsonip]

The docs is very content rich atm, and we should focus on what action the release manager has to take. In this case, if DRA is automated, we should clearly state that DRA is automated and we only have to check that it is green. I'm not sure about qualifier in this case. Probably under a "if DRA is not triggered automatically section"