esteele
(Eric Steele)
December 31, 2018, 1:23am
1
Plone 5.2a2 has been soft-released. Please give it a try and let me know if there are any critical issues. http://dist.plone.org/release/5.2a2-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.
1 Like
pbauer
(Philip Bauer)
December 31, 2018, 1:19pm
3
esteele
(Eric Steele)
December 31, 2018, 3:08pm
4
That should be http://dist.plone.org/release/5.2a2-pending/versions.cfg . 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 dist.plone.org filesystem.
Rotonen
(Joni Orponen)
December 31, 2018, 3:32pm
5
$ curl -H 'Host: dist.plone.org' -XPURGE http://dist.plone.org/release/5.2a2-pending/versions.cfg
<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>cloudflare-nginx</center>
</body>
</html>
Are you sure of the file ownership and permissions?
esteele
(Eric Steele)
December 31, 2018, 5:02pm
6
Yeah, they match all of the other directories/files in /release.
Rotonen
(Joni Orponen)
January 3, 2019, 12:13pm
7
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 dist.plone.org do that too?
tkimnguyen
(T. Kim Nguyen)
January 3, 2019, 8:19pm
8
Sorry for missing this. We/I changed the IP address for dist.Plone.org to the new Six Feet Up VM. Ping me directly via email or here
We've just now made a change to the dist.plone.org IP address. Hopefully you will not notice anything when you next run buildout! Both http and https seem to be working to the new IP address. This change was necessary to prepare for a physical server move.
If you run into any issues connecting with dist.plone.org , please respond here or via email to admins@plone.org
We thank Six Feet Up for continuing to help Plone by serving both dist.plone.org and old.plone.org !
esteele
(Eric Steele)
January 4, 2019, 2:46pm
10
Ah! That'd do it. I sent you an email.
esteele
(Eric Steele)
January 4, 2019, 9:51pm
11
1 Like
zopyx
(Andreas Jung)
January 5, 2019, 7:55am
12
3 Likes
pbauer
(Philip Bauer)
January 5, 2019, 9:31am
13
5.2a2 looks good in my tests.
zopyx
(Andreas Jung)
January 7, 2019, 7:17am
14
I like to see a new release of plone.outputfilters filters containing my bugfix for
esteele
(Eric Steele)
January 8, 2019, 3:45am
15
Added plone.outputfilters 3.1.1 and plone.app.locales 5.1.12. Removed the pending tag.
zopyx
(Andreas Jung)
January 8, 2019, 5:26am
16
Another Python 3 compatibility fix pending for plone.recipe.zeoserver:
zopyx
(Andreas Jung)
January 8, 2019, 6:16am
17
The generated bin/instance
command does not work for 5.2a2 (bin/wsgi.py is working fine):
Plone 5.2a2, plone.recipe.zope2instance 6.0.0 (under Python 3):
bin/instance fg
Error: 'http-header-max-length' is not a known key name
(line 9 in file:///home/ajung/sandboxes/onkopedia_buildout-plone5/parts/instance/etc/zope.conf)
For help, use bin/instance...
01 type: bug
21 status: confirmed
31 needs: help
tisto
(Tisto)
January 14, 2019, 9:16pm
19
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.