cloud-fan opened a new pull request, #56504:
URL: https://github.com/apache/spark/pull/56504

   ### What changes were proposed in this pull request?
   
   Adds a "Versioning and Branch Policy" section to `AGENTS.md` so coding 
agents pick the correct target version for a PR (used for `@since` annotations, 
config `.version("...")` entries, new `MimaExcludes` sections, etc.).
   
   The documented policy:
   - Most PRs merge to **both** `master` and the latest rolling maintenance 
branch `branch-<N>.x`; only breaking / binary-incompatible changes and 
non-critical dependency upgrades go to `master` only.
   - Therefore a change's first release version comes from `branch-<N>.x`, 
**not** from `master` -- deriving it from `master`'s `-SNAPSHOT` alone is the 
common mistake.
   - How to determine the version (decide target branches, then take the oldest 
branch the change lands on with `-SNAPSHOT` stripped), plus the commands to 
find the latest maintenance branch and its version.
   
   ### Why are the changes needed?
   
   `AGENTS.md` guides coding agents working in this repo. Without this, an 
agent reading only `master` (currently `5.0.0-SNAPSHOT`) would label a 
normally-backported change `@since 5.0.0`, when it actually ships first in the 
`branch-4.x` release (`4.3.0`).
   
   ### Does this PR introduce _any_ user-facing change?
   
   No (documentation for coding agents only).
   
   ### How was this patch tested?
   
   N/A (documentation only).
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8)
   
   This pull request and its description were written by Isaac.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to