Release Plan for version 17.10.11
Last modified by Vincent Massol on 2026/07/30 15:50
Release Date: 29/07/2026
Released by:
Information
Use these icons to mark the release progress: 
not done, 
done, 
not done for a good reason (explain reason)
- Verify that no tests are failing on the CI Server (or that failures are understood, see known flickering tests).
- Verify that the xwiki-commons's top level POM has a xwiki.compatibility.previous.version property correctly pointing to the latest stable (non-milestone) release and if not, change it.
- Verify that there are no JIRA issues that are still open, even if they have commits.
- Make sure next version exists on jira projects (JIRA releases are done automatically in the build):
- Verify that there are no open issues on JIRA for version 17.10.11 and that there are no open Blockers.
- Log on the release machine, set up your identity, update the release scripts
- Build the release
- Publish computed list of updated languages in the Release Notes for version 17.10.11
- Publish contributors list in the Release Notes for version 17.10.11
- Publish backward compatibility reports in the Release Notes for version 17.10.11
- Update backward compatibility setup in the build
- Clean up your identity
- Verify that there are no missing documentation for closed JIRA issues for version 17.10.11
- Create (or reuse from the previous RC release) the release dashboard in the Release Notes for version 17.10.11 (don't forget to handle previous bug fix releases in the query)
- If there are security issues (note that this URL might be wrong in case of previous bug fix release, check the dashboard then), indicate it in the summary of the release notes for version 17.10.11.
- Ensure that the Release Notes are complete and nice-looking for version 17.10.11
- Set the Release date + Release flag in the Release Notes for version 17.10.11 by editing with the object editor.
- Force rebuild of the Debian repository index
- Update the Versions page (Use bullets points for the major features to make it easy to read; Update/Bump the LTS if doing a final major version release, i.e. new cycle)
- Force extensions update
- Create blog post on xwiki.org
- Update Wikipedia (en) only if this version is bigger than the existing one.
- Update Wikimatrix, with your own account, only if this version is bigger than the existing one.
- Announce on Mastodon with the xwikiorg account
- Update the Release Plan page to move yourself to the bottom of the list for your next release.
- Mention on Matrix the next 2 release managers in the list so that they're aware about their next duty.
- Ensure that the release date in this Release Plan corresponds to the date when the git release was done
- Update the XWiki official Docker images
