Plone 5.2 final has been soft-released. Please give it a try and let me know if there are any critical issues. https://dist.plone.org/release/5.2-pending/versions.cfg
For those who haven't run across soft-releases before, this is the last step before the final release. Because things haven't been finalized yet, some packages may change between now and the release. It is not recommended to use soft-releases in production.
Thank you very much!
I have a buildout complaining about a missing pin:
# Required by:
# plone.recipe.zeoserver==2.0.1
ZopeUndo = 4.3
Not even sure if ZopeUndo should be still a requirement
@vincentfretin It looks like we've had some more translations come in since rc5. Would you mind creating a new plone.app.locales release?
plone.app.locales 5.1.18 released.
ZopeUndo used to be pinned by http://dist.plone.org/versions/zope-2-13-27-versions.cfg. We should add it to our pinns in versions.cfg.
Done in https://github.com/plone/buildout.coredev/commit/f88c2485854099b8b38386ec52813b93d0144243
@jensens do we need to update plomne.app.multilingual and archetypes.multilingual for 5.2 final or can this wait until 5.2.1?
@esteele plone.app.contenttypes has a small improvement of AT-DX migrations without side-effects that could be released and added to 5.2. But it can also wait until 5.2.1.
I would like to have a release of plone.app.multilingual, but it it is not needed to include it in 5.2.0. archetypes.multilingual can wait.
I've pushed a new versions.cfg that includes:
@jensens I cut a 5.4.0 release of plone.app.multilingual, but didn't include it in this release.
Thanks, it works fine.
And we're done. I've removed the pending flag and sent 5.2 on to the installers team.
Fantastic work, everyone!
The official Plone demo site http://demo.plone.org is now running 5.2 final.
Also: https://github.com/starzel/buildout now supports 5.2
The Unified Installer for 5.2.0 is now available at https://launchpad.net/plone/5.2/5.2/+download/Plone-5.2.0-UnifiedInstaller.tgz
Note: the installer no longer includes a complete buildout cache, so it's a much faster download. And, if there are a full set of wheels available for your platform, the build speed isn't much affected.
Thanks!
It's been a while since I've looked at the Travis builds. I know they used to reference the buildout cache in the installer repo. Is that still the case and should we be providing that elsewhere now?
Here's a pull request for the 5.2.0 docker images:
The Vagrant kit is now also updated and the links on the release page added.
It's been a while since I've looked at the Travis builds. I know they used to reference the buildout cache in the installer repo. Is that still the case and should we be providing that elsewhere now?
I don't know if the references still exist, but the time advantage of using the cache is now small or non-existent. That's partly because the cache would be much larger to include both 2.7 and 3.x and partly because the pervasive availability of wheels removes much of the pre-cooking advantage of the cache.
And, the Ansible toolkit's STABLE branch is updated for 5.2. It also adds support for Python 3 via specification of plone_python_version variable globally or per Plone instance.
