lukaszlenart opened a new pull request, #1826: URL: https://github.com/apache/struts/pull/1826
Adds a `creating-version-notes` skill covering Version Notes pages on the Struts cwiki, alongside the existing `creating-security-bulletins` skill. ## One skill, both lines Comparing the storage format of [Version Notes 6.10.0](https://cwiki.apache.org/confluence/spaces/WW/pages/430407834) and [Version Notes 7.2.1](https://cwiki.apache.org/confluence/spaces/WW/pages/430409086): the intro, prior-notes link, TOC, Maven section, both code macros, issue-type sections, Issue Detail, Issue List and Other resources are identical. Only two blocks vary — Breaking changes and Staging Repository — and neither is line-specific. So the release line changes the data, not the process. ## Why a template rather than copying the last page Every recent page carries a defect inherited by cloning, in a different place each time: | Page | Inherited defect | | ---- | ---------------- | | Version Notes 6.9.0 | Issue Detail links "JIRA Release Notes **6.8.0**" — label and `version=` id both from 6.8.0 | | Version Notes 6.10.0 | Issue List links "Struts **6.9.0** DONE" on the 6.10.0 page | | Both series | Maven Dependency code macro carries `ac:name=""` instead of `ac:name="language"` | The template corrects the malformed macro parameter, drops the hard-coded `ac:macro-id`s that are duplicated across releases and series, and drops the two empty trailing `<div>`s every page ends with. ## What the skill covers beyond the mechanics - **Reconciling the issue list against the release branch** — JIRA is the claim, the branch is the fact. - **Released versions only in the prior-notes chain** — 7.2.1 links back to 7.1.1, skipping the withdrawn 7.2.0, and absorbed its Breaking changes. Same discipline `creating-security-bulletins` applies to Affected Software. - **Security fixes in a release** — the notes list a public, neutrally-framed ticket while the bulletin is still restricted; no unpublished severity, CVE or S2-XXX reference. Cross-references `creating-security-bulletins`. - **Breaking changes as authored prose**, not pasted ticket summaries. ## Open point for the release manager The Staging Repository block is present on 7.1.1 and 7.2.1 and absent on 6.9.0 and 6.10.0 — it tracks the series rather than the release phase, which given the cloning pattern suggests it propagated rather than being chosen. The skill therefore treats including it as an explicit decision and asks for confirmation on whether it stays after a release is announced, rather than inventing a policy. ## Testing Not exercised against subagent scenarios; the skill's guidance is derived from the four published pages cited above, and the storage-format skeleton is transcribed from them with the listed defects corrected. Same posture as the `creating-security-bulletins` skill. 🤖 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]
