Branch: refs/heads/contrib-release-notes-are-on-exo Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3f2906e93cb2ea8578ed3998d9253559a5da8c8a https://github.com/xwiki/xwiki-dev-llm/commit/3f2906e93cb2ea8578ed3998d92535... Author: Vincent Massol <[email protected]> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M xwiki/okf/index.md M xwiki/okf/processes/release-notes.md M xwiki/okf/servers/jira.md M xwiki/skills/xwiki-release-documentation/SKILL.md Log Message: ----------- [Misc] Record where a non-bundled extension's release notes live * An extension that is not bundled in XWiki Standard does not use the Release Notes Application on xwiki.org: its release notes are the Repository application's per-version ones on extensions.xwiki.org — the `notes` property of `ExtensionCode.ExtensionVersionClass` on the hidden version page, rendered in the extension page's Versions section — and in practice a `{{jira}}` macro over the fix version. So such an issue owes no release-note entry, takes `N/A` in `Documentation in Release Notes`, and owes nothing at all until the version is released. `okf/processes/release-notes.md` gains the section and a `verify:` that reads a version's notes back; `okf/servers/jira.md` and `okf/index.md` route to it; the `xwiki-release-documentation` skill's Scope section says it instead of leaving contrib merely "out of scope". * Both documentation fields are capped at 255 characters (`okf/servers/jira.md`) — three documentation URLs do not fit one field. * The Release Notes Application's REST resources carry `GET` and `POST` only *in 2.7*; `GET` and `PUT` on one release note and on one change were added after it, and a `PUT` replaces rather than merges. Corrected in the endpoint list and where the skill's §6.2 sets `screenshots`. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications