New Release Plan for version $request.version

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.clirr.previous.version property correctly pointing to the latest stable (non-milestone) release and if not, change it and ensure that all the CLIRR excludes are correct and remove those that are no longer valid.
•  Verify that there are no open issues on JIRA for version $version
•  Verify that no tests are failing on the CI Server (or that failures are understood).
•  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
• Release JIRA versions for the following JIRA projects:
  • Commons JIRA
  • Rendering JIRA
  • Platform JIRA
  • Enterprise JIRA
•  Since the release is performed on agent-1-1, mark it offline in the  Jenkins admin screen. Put as comment Temporarily marking agent-1-1 offline for the release of $version.
• 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 CLIRR reports in the Release Notes for version $version
• Push distribution files to OW2 and release them
•  Update the XE Download page
•  [OPTIONAL] You can force update extensions on http://extensions.xwiki.org using the Batch importer scheduler
•  Ensure that there's a line pointing to the Release Notes for version $version 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)
• FreeCode (you can check previous releases)
• Wikimatrix with Ludovic's account
• Announcement Mail
• Announce on Twitter with the xwikiorg account
•  Add yourself to the Release Manager Roster page
•  Update the release date on the Roadmap page for non bugfix releases
• Push Commons and Rendering to Maven Central