From 8ce6b5c8c7eb13884d6c64ed9f7428c4efaeed18 Mon Sep 17 00:00:00 2001 From: Paul Barker Date: Mon, 10 Aug 2026 09:38:15 +0100 Subject: [PATCH] contributor-guide: Note patch complexity requirements for stable branches Expand the existing note section under "Submitting Changes to Stable Release Branches" to provide guidance on (not) submitting large or complex changes. Concerns around the increased size and complexity of patches being submitted for the stable branches (mostly driven by complex vulnerabilities found and/or fixed via LLM agents) were discussed with the stable maintainer and the Yocto Project TSC. This patch reflects the TSC decision that we should push back on these changes to preserve the maintainability of our stable branches. Cc: Yoann Congal (From yocto-docs rev: 3adedbd203b894924fb75d187a8cea1d92aaa700) Signed-off-by: Paul Barker Signed-off-by: Antonin Godard (cherry picked from commit 33bf0ff80df6be2aad8eb081752648d3c408a54b) Signed-off-by: Antonin Godard Signed-off-by: Paul Barker --- documentation/contributor-guide/submit-changes.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst index 43c5abe20e..7f091c39e9 100644 --- a/documentation/contributor-guide/submit-changes.rst +++ b/documentation/contributor-guide/submit-changes.rst @@ -702,6 +702,12 @@ page. .. note:: + Patches submitted for a stable branch need to be isolated changes that are + human readable and understandable. Fixes for CVEs or other issues which have + a high complexity, consist of a large number of commits and/or a large + numbers of changed lines are unlikely to be accepted due to the difficulty + they cause with maintainability and scalability. + Changes will not typically be accepted for branches which are marked as End-Of-Life (EOL).