On behalf of Zope developer community I am pleased to announce the release of the first alpha release of the Zope 5 series: 5.0a1
Zope 5 drops support for
Python 2.7, it supports Python 3.5 up to 3.8
ZServer, it is now WSGI only
To migrate to Zope 5: first migrate to the lastest Zope 4 release.
If your code runs on the WSGI stack without showing deprecations warnings it should also be able to run on Zope 5, too, without changes.
All other changes (besides these non-backwards compatible ones) have been back ported to Zope 4.x.
(We will keep doing so until the final Zope 5 release.)
There is a separate project underway to port ZServer to Python 3 and make it compatible with the Zope WSGI stack. If and when the project reaches maturity we will help integrate this new ZServer into Zope.
This probably refers to my Twisted ZServer fork. There has not been progress lately, because I have been off from suitable projects, but it has not been abandoned and my intention is to run our future Python 3 Plone projects on it. That said, there will be major refactoring in my fork once Plone has been migrated to the latest Zope 4.x with restored WebDAV support. Those interested to try it out, can ping me.
As I already said in the issue tracker issue you created for this: Your use case, full WebDAV file system support, has never been supported by the Zope WebDAV code and most likely will never be supported. It can do whatever it did in Zope 2.13. The goals are entirely different here.