New Release Plan for version $request.version
Last modified by Vincent Massol on 2017/07/12 09:42
Release Date:
Released by:
Use these icons to mark the release progress: 
not done, 
done, 
not done for a good reason (explain reason)
not done, done, not done for a good reason (explain reason)- 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.
- Make sure next version exists on jira projects (JIRA releases are done automatically in the build):
- Commons JIRA
- Rendering JIRA
- Platform JIRA
- [Only for 8.4.x] Enterprise JIRA
- Verify that there are no open issues on JIRA for version $version and that there are no open Blockers.
- Verify that no tests are failing on the CI Server (or that failures are understood, see known flickering tests).
- Verify that there are no missing documentation for closed JIRA issues for version $version
- Ensure that the Release Notes are complete and nice-looking for version $version
- Since the release is performed on agent-1-1, mark it offline in the Jenkins admin screen to avoid using it in the CI. Put as comment Temporarily marking agent-1-1 offline for the release of $version.
- Log on the release machine, set up your identity, update the release scripts and set the correct Java version
- Update translations
- Build the release
- Clean up your identity
- Mark agent-1-1 online again in the Jenkins admin screen (button on the right).
- Publish backward compatibility reports in the Release Notes for version $version
- Publish code contributors list in the Release Notes for version $version
- Push distribution files to OW2 and release them
- 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
- Set the Release date + Release flag in the Release Notes for version $version by editing with the object editor.
- Create blog post on xwiki.org
- Update the API doc, including Rendering
- Update Wikipedia (en), Wikipedia (fr) and Wikipedia (compare wiki software)
- Wikimatrix with Ludovic's account
- 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 release was finished
- Update the release date on the Roadmap page for non bugfix releases and move the roadmap items to the archive page (for final releases)
- Push Commons and Rendering to Maven Central
- Update the XWiki official Docker images
