This is an automated email from the ASF dual-hosted git repository.

jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/main by this push:
     new 5788612385 chore: backport targets are the LTS lines only
5788612385 is described below

commit 57886123852b2ecaa5b0b7cdcc8f3ec8f3b0a849
Author: Andrea Cosentino <[email protected]>
AuthorDate: Mon Sep 7 08:07:06 2026 +0200

    chore: backport targets are the LTS lines only
    
    The list added in #9074 named 3.39.x as a backport target because it was the
    most recently active branch. It is not an LTS line, and a backport to it was
    declined on those grounds in #9084, so the rule as written sends the next
    reader into a PR that gets closed.
    
    Narrow the targets to main plus the LTS lines, note that 3.40.x becomes the
    next LTS, and say plainly that neither a branch's presence in git branch -r
    nor how recently it was committed to tells you whether it is a target - the
    newest active branch is usually the current non-LTS release line, which is
    what caused the mistake.
    
    
    Claude-Session: https://claude.ai/code/session_01Nvs8UTajTMYsXa2rcHdiRz
    
    Co-authored-by: Claude Opus 5 <[email protected]>
---
 .oss-ai-helper-rules/project-guidelines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.oss-ai-helper-rules/project-guidelines.md 
b/.oss-ai-helper-rules/project-guidelines.md
index d42d9adbc0..fc8de16149 100644
--- a/.oss-ai-helper-rules/project-guidelines.md
+++ b/.oss-ai-helper-rules/project-guidelines.md
@@ -12,7 +12,7 @@ This rule file contains branching, commit, PR, and 
task-finding conventions for
 - **CI-issue branch:** `ci-issue/<short-slug>`
 - **Commit format (ci-issue):** `ci: <brief description>`
 - **PR creation:** always
-- **Backport targets:** `main`, `3.39.x` (current release line), `3.33.x` 
(LTS), `3.27.x` (LTS). Camel Quarkus follows the **Quarkus LTS cadence**, so 
each line pairs with a Quarkus version (3.33.x ↔ Quarkus 3.33.x, 3.27.x ↔ 
Quarkus 3.27.x). `3.20.x` and `3.15.x` are older LTS lines that are no longer 
routinely maintained — do not open backport PRs against them without checking 
first. **A branch existing in `git branch -r` is not evidence that it is 
supported**: every `3.N.x` branch ever [...]
+- **Backport targets:** `main`, plus the **LTS lines only** — currently 
`3.33.x` and `3.27.x`. `3.40.x` becomes the next LTS. Camel Quarkus follows the 
**Quarkus LTS cadence**, so each LTS line pairs with a Quarkus LTS version 
(3.33.x ↔ Quarkus 3.33.x, 3.27.x ↔ Quarkus 3.27.x). Non-LTS release lines are 
**not** backport targets, however recently they were released: a backport to 
`3.39.x` was declined for exactly this reason (#9084). `3.20.x` and `3.15.x` 
are older LTS lines that are no l [...]
 
   ```sh
   # %cd (committer date), not %ad: a cherry-picked backport keeps the original

Reply via email to