Skip to content

docs(skills): send the [TEST] mail from the @apache.org identity #1963

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukaszlenart merged 2 commits into from
Sep 18, 2026
+8 −0
Merged

docs(skills): send the [TEST] mail from the @apache.org identity #1963

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a5847a
docs(skills): send the [TEST] mail from the @apache.org identity
lukaszlenart Sep 17, 2026
e1a845f
docs(skills): name the @apache.org identity, not one committer's address
lukaszlenart Sep 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .claude/skills/creating-version-notes/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,6 +272,13 @@ Kind regards

Do not take the recipients from a previous announcement: 6.11.0 went to `dev@` alone and 7.3.0 to `user@` alone, and both were mistakes. Address every announcement to the two lists above.

**It is sent from the release manager's `@apache.org` address, and the draft cannot say so.** The
Gmail draft tool has no sender field, so every draft it creates carries the account's default address,
which may be a personal one. When handing the draft over, say in the same sentence that the From must be
switched to the `@apache.org` identity before sending — a test build announced from a personal address
reads as an outsider's mail in the list archive, and `creating-release-vote-mail` needs the same switch
for the `[VOTE]`.

Keep the security posture of the pages: the mail links the release notes, it does not summarise what is in them, so no severity, CVE or S2-XXX reaches it either.

**The vote is the next step, and it is a different mail.** Once the test build is announced, `creating-release-vote-mail` composes the `[VOTE] Apache Struts X.Y.Z` call — to `dev@` alone, rendered from the page this skill produced. Do not draft it from here: its recipients, subject and body all differ from the announcement above.
Expand Down
1 change: 1 addition & 0 deletions .claude/skills/creating-version-notes/version-notes-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,3 +150,4 @@ Repeat the issue `<h2>` block per type present, in the order given above.
- [ ] Addressed to **both** `dev@struts.apache.org` and `user@struts.apache.org`, Bcc `private@struts.apache.org`.
- [ ] Risk clause matches reality: silent when there are no Breaking changes, "but it contains significant changes" when there are.
- [ ] Tag underscored in the release link, version dotted in the dist path and page title.
- [ ] Hand-over says to switch the From to the release manager's `@apache.org` address — the draft tool cannot set it.
Loading