Myasnikov Daniil c12dcdddb4 docs(release): make backports automatic, by written rules ...

Backports were asked for pull request by pull request with labels and
opened by a bot, so whether a fix reached a release line depended on
someone remembering to ask, and the lines drifted apart. The policy
page states the rules instead: a fix or security fix merged into main
goes to every line the batch runs for, unless it is breaking, touches
platform migrations or a CRD, or changes the API in a way the API
review gate calls sizeable. Two labels let a maintainer override the
rules for one pull request.

The task pages give a maintainer the steps for a deferred conflict and
for a failed batch CI. The backports route in AGENTS.md, the
contributing and changelog guides and the PR template point at the
policy, and the commit format lists the security type the policy
takes.

Assisted-By: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-11-06 12:33:35 +00:00

..

changelog.md

docs(release): make backports automatic, by written rules

2026-11-06 12:33:35 +00:00

contributing.md

docs(release): make backports automatic, by written rules

2026-11-06 12:33:35 +00:00

e2e-testing.md

ci(api-review-gate): build the fork detector from the default branch

2026-11-02 14:47:51 +05:00

image-refs.md

feat(release): attach an SBOM to every release image

2026-10-20 16:40:06 +05:00

overview.md

docs(release): split the release document into one page per topic

2026-11-04 15:03:06 +00:00

releasing.md

docs(release): make backports automatic, by written rules

2026-11-06 12:33:35 +00:00