[S] Change in asterixdb[morpheus]: [NO ISSUE][MISC] += no downstream detail in bodies

[AsterixDB Code Review <do...@asterix-gerrit.ics.uci.edu>]

From Michael Blow <mb...@apache.org>:

Michael Blow has uploaded this change for review. ( https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/21719?usp=email )


Change subject: [NO ISSUE][MISC] += no downstream detail in bodies
......................................................................

[NO ISSUE][MISC] += no downstream detail in bodies

This repo's Gerrit and Jira are public and upstream of the extensions
that consume it, so a commit body written here is published beyond the
extension it was written for. Record that a body describes only what
changed in this repo, that the `Ext-ref:` footer and a generated merge
list's appended ids are the only place a downstream issue id belongs,
and that reasoning about an extension's own side of a coordinated change
stays in that extension's half of it.

Co-Authored-By: Claude Opus 5 <no...@anthropic.com>
Change-Id: Ia6aa8d55d166caadc55e1cbccc74475cd917a0b3
Ext-ref: MB-68099
---
M CLAUDE.md
1 file changed, 13 insertions(+), 0 deletions(-)



  git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/19/21719/1

diff --git a/CLAUDE.md b/CLAUDE.md
index 9675d2b..9591e89 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -95,6 +95,19 @@
 Change-Id: I...
 ```
 
+**Keep downstream detail out of the message body.** This repo's Gerrit and Jira are public, and
+upstream of any extension that consumes it, so a commit body describes only what changed *here*:
+which property moved, which files, what a merge carried. A downstream extension's product names,
+branch-as-product names, issue ids, packaging, licensing and back-compat machinery do not belong
+in it. The `Ext-ref:` footer is the sole place a downstream issue id goes — together with the
+`(<id>)` that an extension's merge tooling appends to each bullet of a generated missing-commits
+list, which is read from that footer and should be left as generated. Where such an id already
+sits inside a subject this repo has published, it is history and stays as it is.
+
+A merge commit's body is that generated bullet list and the trailers, nothing more. Reasoning
+about a downstream extension's side of a coordinated change belongs in that extension's own half
+of it.
+
 Two ways the footer gets destroyed, both of which make the `commit-msg` hook mint a **second**
 `Change-Id` and silently orphan the change:
 

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/21719?usp=email
To unsubscribe, or for help writing mail filters, visit https://asterix-gerrit.ics.uci.edu/settings?usp=email

Gerrit-MessageType: newchange
Gerrit-Project: asterixdb
Gerrit-Branch: morpheus
Gerrit-Change-Id: Ia6aa8d55d166caadc55e1cbccc74475cd917a0b3
Gerrit-Change-Number: 21719
Gerrit-PatchSet: 1
Gerrit-Owner: Michael Blow <mb...@apache.org>