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

HyukjinKwon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark-connect-rust.git


The following commit(s) were added to refs/heads/master by this push:
     new 7573b35  [MINOR][DOCS] Document the connect-rust-x.y.z JIRA version 
convention in AGENTS.md
7573b35 is described below

commit 7573b35539be4f273d8f964b90d27d9d7b861b22
Author: Hyukjin Kwon <[email protected]>
AuthorDate: Fri Aug 28 16:50:53 2026 +0900

    [MINOR][DOCS] Document the connect-rust-x.y.z JIRA version convention in 
AGENTS.md
    
    ### What changes were proposed in this pull request?
    
    Adds a golden-rule bullet to `AGENTS.md` (section 0) stating that JIRAs for
    spark-connect-rust always use the `connect-rust-x.y.z` version line (never 
the
    core Spark `x.y.z` line) for **both** the *Affects Version/s* and *Fix
    Version/s* fields.
    
    ### Why are the changes needed?
    
    spark-connect-rust ships on its own `connect-rust-*` release line so its 
JIRAs
    land in the connect-rust release notes instead of leaking into core Spark's.
    `dev/create_spark_jira.py` and `dev/merge_connect_rust_pr.py` already 
enforce
    this; documenting it in `AGENTS.md` keeps hand-filed/hand-edited tickets
    consistent with the tooling.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No. Documentation only (agent-facing guidance).
    
    ### How was this patch tested?
    
    N/A — documentation-only change.
    
    This pull request and its description were written by Isaac.
    
    Closes #77 from HyukjinKwon/agents-md-jira-version-convention.
    
    Authored-by: Hyukjin Kwon <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 AGENTS.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index d2bdf90..0008da9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -69,6 +69,13 @@ the Rust and Python sides, no stubs, green CI.
   — resolves the JIRA, and pushes to the `apache` remote's `master`. It is
   interactive; drive it by piping the prompt answers on stdin (e.g. the PR 
number,
   then `y`/`n`/blank for the confirmations, author default, and "Push to 
apache?").
+- **JIRA version convention: always `connect-rust-x.y.z`, never the core Spark
+  `x.y.z` line.** When you file a JIRA for spark-connect-rust, set **both** the
+  *Affects Version/s* and the *Fix Version/s* to a `connect-rust-x.y.z` version
+  (e.g. `connect-rust-0.1.0`, `connect-rust-4.2.0`) — never a core Spark 
version.
+  This keeps connect-rust work in its own release notes instead of leaking into
+  core Spark's. `dev/create_spark_jira.py` and `dev/merge_connect_rust_pr.py`
+  already follow this; keep it consistent when editing tickets by hand.
 
 ## 1. Environment setup
 


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

Reply via email to