Release checklist Plone 5.2.5

[mauritsvanrees]

See the release schedule.

• Check Jenkins Status: should be green. (This should be checked often during the release process.)
• In coredev, check packages for updates: bin/manage report --interactive
• Release individual packages from checkouts.cfg.
• Check that the version numbers of CMFPlone metadata.xml and latest upgrade step are in sync, and that they are higher than in the Plone release.
• If unsure, ask if mockup and plone.staticresources are in sync and can be released. Example: Release for 5.2.3 mockup#1026
• If needed, ask the Plone REST api team for a new release of plone.restapi and plone.rest.
• Write an email to the translation team, asking them to do a plone.app.locales release. Or create an issue in https://github.com/collective/plone.app.locales/issues
• Update the versions of those packages. #3307
• Make an release candidate release of Products.CMFPlone (e.g. 5.2.5rc1). Fine to release this on PyPI.
• Create a coredev branch, named something like prepare-525. Empty the auto-checkout list in checkouts.cfg.
• Create a pending release (directory) on dist.plone.org, e.g. 5.2.5-pending, and gather files to put there:
  • Create a unified changelog: bin/manage changelog --start=5.2.4 > changelog.txt. Remove the uninteresting top lines.
  • Create a RELEASE-NOTES.txt. It may be enough to look through the changelog and copy interesting changes.
  • Gather all package distributions.
    You can use tox -c release/tox.ini -p auto to gather them in release/dist, together with a few other files.
  • Get the versions.cfg file from coredev.
  • Create a constraints.txt from this. The above tox command generates this and puts it in release/dist.
  • Copy (rsync) all core packages and the other files to the pending release directory. I think we mostly do this so we have a backup if a version gets removed from PyPI.
• Write a post on community.plone.org announcing a pending/soft release.
• Wait for feedback, preferably at most a few days.
• Make final release of Products.CMFPlone to PyPI, update versions.cfg.
• Create tag of the release branch, e.g. 5.2.5, and push to GitHub.
• Make final release on dist.plone.org (remove "-pending", make sure updated distributions, versions and constraints are added).
• Update the "-latest" link on dist.plone.org
• Create new release on launchpad (https://launchpad.net/plone/): bin/manage launchpad <version>
• Create release page on https://plone.org/download/releases
• Announce community.plone.org, with warning that installers are not ready yet: https://community.plone.org/t/plone-5-2-5-released/14176
• Send links to installers list
• Wait for installers to be uploaded to Launchpad, link on plone.org release page
• Publish release page on plone.org. If the installer takes too long, publish it anyway. Coordinate with the Marketing Team.
• Marketing Team: Send out announcement to plone-announce, Twitter, update #plone irc channel topic, what you want.
• Ask the security team to update the https://plone.org/security/hotfixes/ page in the configuration control panel. (Configuration registry: plone.securitysupport, plone.versions, plone.activemaintenance)

[mauritsvanrees]

Unified Installer is finally there.