Skip to content

docs(skills): carry the 7.4.0 / 6.12.0 advisory lessons into the release skills - #1987

Merged
lukaszlenart merged 1 commit into
mainfrom
docs/skills-phase7-lessons
Oct 5, 2026
Merged

lukaszlenart merged 1 commit into
mainfrom
docs/skills-phase7-lessons

Conversation

@lukaszlenart

Copy link
Copy Markdown
Member

Folds what the 7.4.0 / 6.12.0 advisory round (S2-075 … S2-078) taught into the three release skills.

How the gaps were found

Four scenarios were run against the skills on main, with project memory off-limits so only the skills were tested. Each failed:

Scenario Behaviour on main
Release finishes on a Friday, release manager wants phase 7 closed before the weekend Nothing in the skills holds advisories over a weekend — the rule existed only in personal memory
Bulletins just went public, "update the Version Notes" "the notes may link it" produced bulletin links inline in the Bug / Improvement lists, no dedicated section
Fill a freshly reserved CVE record No guidance on the record's fields: ranges merged across maintenance lines, title double-prefixed with Apache Struts:
Advisory mails sent — "what's left?" Nothing past the send button: reporter notices, the site PR and the THREAT_MODEL.md §12 re-baseline check went unmentioned

The same four scenarios rerun against this branch all pass, and the CVE-record and Version Notes outputs match what was actually published for S2-075 … S2-078.

Changes

  • creating-security-bulletins
    • Publish at the start of a working week — no unrestrict, READY or send on a Friday or before a holiday; prepare and propose Monday.
    • Filling the CVE record — the house JSON shape (one versions entry per bulletin line, Maven packageURL, text severity with the GENERAL scenario, four-part description, CWE chosen and named to the release manager), the JSON-editor write path, and READY as the PMC's last step.
    • After the advisory mails — Version Notes Security section, site PR, one reporter notice per report thread, the threat-model check.
    • Red flags for each, and a description that triggers on CVE-tool work and post-publication wrap-up.
  • creating-version-notes — the Security section: placement after Maven users, line format, and the section-update write path; section order, checklist and red flags updated.
  • releasing-struts — phase 7 gate names the working-day rule and the follow-ups; the ordering states that ASF Security pushes to MITRE.

🤖 Generated with Claude Code

…ase skills

Four baseline scenarios run against the previous skills, with project
memory off-limits, each failed:

- Friday publication: no skill held advisories over a weekend; the
  rule existed only in memory.
- Version Notes after publication: "the notes may link it" led to
  inline bulletin links in the type sections, no Security section.
- CVE record: nothing on the record's fields, so ranges were merged
  across lines and the title double-prefixed.
- After the mails: nothing past the send button; reporter notices,
  the site PR and the THREAT_MODEL.md section 12 check went unmentioned.

creating-security-bulletins gains a publication-day rule, a "Filling
the CVE record" section (house JSON shape: one range per bulletin line,
Maven purl, text severity with the GENERAL scenario, four-part
description, JSON-editor write path, READY as the PMC's last step) and
an "After the advisory mails" checklist. creating-version-notes defines
the Security section, its place and its line format. releasing-struts
updates the phase 7 gate and the publication ordering.

The same four scenarios rerun against these edits all pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lukaszlenart
lukaszlenart marked this pull request as ready for review October 5, 2026 13:36
@lukaszlenart
lukaszlenart merged commit e3613f9 into main Oct 5, 2026
13 checks passed
@lukaszlenart
lukaszlenart deleted the docs/skills-phase7-lessons branch October 5, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant