Plone 5.2a2 released

Plone 5.2a2 has been soft-released. Please give it a try and let me know if there are any critical issues.

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.

1 Like

The link is not working.

@esteele: Confirmed. The folder does not exist.

That should be I fixed the link in the original post.

I'm still getting a 404 on that one though. I can confirm everything looks correct on the filesystem.

$ curl -H 'Host:' -XPURGE
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>

Are you sure of the file ownership and permissions?

Yeah, they match all of the other directories/files in /release.

That means I'm not sure on how Cloudflare is set up and that 403 is truly from the cache. Does it currently only allow for cache purging via the web clickety admin UI? PyPI allows for anonymous PURGE requests. Should do that too?

Sorry for missing this. We/I changed the IP address for to the new Six Feet Up VM. Ping me directly via email or here

Oh man!

Ah! That'd do it. I sent you an email.

Alrighty. We should be good now.

1 Like

now running on 5.2a2


5.2a2 looks good in my tests.

I like to see a new release of plone.outputfilters filters containing my bugfix for

Added plone.outputfilters 3.1.1 and 5.1.12. Removed the pending tag.

Another Python 3 compatibility fix pending for plone.recipe.zeoserver:

The generated bin/instance command does not work for 5.2a2 (bin/ is working fine):

What are the minimum versions of Python 2.7.x and 3.x for Plone 5.2? Need to update and the unreleased 5.2 branch for Thank you!

If I recall correctly you need at least Python 2.7.14 to run ZEO on Plone 5.2.

For Python 3, you can use either Python 3.6 or 3.7. I am not aware of any minimum bugfix releases.