Release Plan for version 11.7
Last modified by Marius Dumitru Florea on 2019/08/27 14:25
Release Date: 27/08/2019
Released by:
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 with commits for this branch and that are not closed
- 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 11.7 and that there are no open Blockers.
- Since the release is performed on agent-1-1 and since it shares memory with other agent1-* agents, mark as offline agent1-1, agent1-2 and agent1-3 to avoid using them in the CI. Put as comment Temporarily marking agent-1-* offline for the release of 11.7.
- Log on the release machine, set up your identity, update the release scripts and set the correct Java version
- Update translations
- Publish computed list of updated languages in the Release Notes for version 11.7
- Build the release
- Publish code contributors list in the Release Notes for version 11.7
- Publish backward compatibility reports in the Release Notes for version 11.7
- Update backward compatibility setup in the build
- Clean up your identity
- Mark agent-1-1, agent-1-2 and agent-1-3 online again (button on the right).
- Verify that there are no missing documentation for closed JIRA issues for version 11.7
- Ensure that the Release Notes are complete and nice-looking for version 11.7
- Set the Release date + Release flag in the Release Notes for version 11.7 by editing with the object editor.
- Force rebuild of the Debian repository index
- Update the Download 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 the API doc, including Rendering
- Update Wikipedia (en), Wikipedia (fr) 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.
- Announcement Mail and Forum Post
- Announce on Twitter with the xwikiorg account
- Update the Release Plan page to move yourself to the bottom of the list for your next release.
- Ensure that the release date in this Release Plan corresponds to the date when the git release was done
- Update the release date on the Roadmap page for non bugfix releases and move the roadmap items to the archive page (for final releases)
- Update the XWiki official Docker images
- Delete the "stable-XXX" branches before the "stable-11.7" ones on github and in Jenkins by using the "Delete branch" UI button when on the branch jobs:
