oscerd opened a new pull request, #9074: URL: https://github.com/apache/camel-quarkus/pull/9074
`.oss-ai-helper-rules/project-guidelines.md` covers branch naming, commit formats and task-finding, but says nothing about which release lines a fix should be backported to. The equivalent rules for `apache/camel` name their backport branches explicitly; this brings Camel Quarkus into line. **What it records** - **Targets:** `main`, `3.39.x` (current release line), `3.33.x` and `3.27.x` (LTS). `3.20.x` and `3.15.x` are older LTS lines that are no longer routinely maintained. - **Method:** cherry-pick, preserving the original author and message — matching how `Fix #9010` reached `3.33.x`. - **Applicability:** confirm the *defect* exists on the target rather than just the file, since extensions differ between lines (`extensions-jvm/diagram`, for instance, does not exist on `3.33.x` or `3.27.x`). - **Migration guides:** `migration-guide/<version>.adoc` is per release line, so a change carrying a note on `main` must not backport that file — the target line needs its own note. **Why it is worth writing down** Every `3.N.x` branch ever released is still present in `git branch -r`, so the listing tells you nothing about which lines are supported. I got this wrong reading it: sorting those branch names lexically suggested the newest maintained line was `3.22.x`, last touched in April 2025, when `3.33.x` and `3.27.x` had both received commits days earlier. The snippet in the new section sorts by **committer** date rather than author date. That distinction matters here specifically: a cherry-picked backport keeps the original author date, so `%ad` ranks `3.38.x` (2026-07-23) above `3.33.x`, which looks like `3.33.x` is the staler line. By `%cd` the LTS lines correctly sort above it, both at 2026-08-19. Documentation only — no build or code impact. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
