Plone 4.3.20 release checklist

[mauritsvanrees]

Release checklist for Plone 4.3.20. This is the final release of 4.3.x. Let's make it a smooth one.
See also the release schedule.

This list is mostly for me as release manager, but feel free to tag an issue as blocker, and link it here in a comment, or add other checklist items or questions/suggestions.

Tag on coredev: https://github.com/plone/buildout.coredev/tree/4.3.20

Here is the checklist, based on https://docs.plone.org/develop/coredev/docs/release.html (see source), but really just a copy of #3119:

• 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. The version number must be higher than from the previous Plone release, otherwise @@plone-upgrade will not do anything, and we may miss upgrades from some core add-ons.
• If unsure, ask if mockup and plone.staticresources are in sync and can be released. [irrelevant for 4.3]
• If needed, ask the Plone REST api team for a new release of plone.restapi and plone.rest. [irrelevant for 4.3]
• 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 plone.app.locales version.
• Create a pending release (directory) on dist.plone.org
  • Copy all core packages there. TODO: is there a handy command for this?
  • Possibly make an alpha/beta release of Products.CMFPlone and put it only on dist.plone.org, not PyPI.
  • Copy files from coredev there: versions.cfg, requirements.txt. Plus constraints.txt and RELEASE-NOTES.txt if you have it.
• Create a unified changelog: bin/manage changelog
• Write a post on community.plone.org announcing a pending/soft release. See example
• Wait for feedback, preferably at most a few days.
• Make final release of Products.CMFPlone to PyPI
• Make final release on dist.plone.org (remove "-pending", make sure updated distributions 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.
• 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
• Update plone.org homepage links to point to new release
• Send out announcement to plone-announce
• Update #plone irc channel topic
• 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)