Release Plan for version 8.1
Last modified by Thomas Mortagne on 2017/03/24 12:15
Release Date: 24/05/2016
Released by:
Use these icons to mark the release progress: 
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.
- Verify that there are no open issues on JIRA for version 8.1.
- 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 8.1
- Ensure that the Release Notes are complete and nice-looking for version 8.1
- Release JIRA versions and create new versions for the next development iteration on the following JIRA projects:
- 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 8.1.
- Log on the release machine, set up your identity and update the release scripts
- 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 8.1
- Push distribution files to OW2 and release them
- Force rebuild of the Debian repository index
- Update the Download page (make sure to use bullets points for the major features to make it easy to read)
- Force extensions update
- Ensure that there's a line pointing to the Release Notes for version 8.1 on the Release Notes home page
- Publish news on OW2
- 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
- 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
