Hi @tkimnguyen et community, we're just before launching a new project which we are developing since 2 months started with Plone 5.2b1 on Python 3. Now it's migrated to 5.2rc2. It uses collective.geolocationbehavior, collective.collectionfilter[geolocation], collective.address and collection.easyform. And we prototyped some TTW generated content-types together with our customer ... everything worked like a charm.
So from my point of view, Plone 5.2rc2 is stable enough for production!
The only thing what I'm not shure about is the deployment but I think that's out of this testing call scope. Just noticed that since a few days there's https://pypi.org/project/supervisor version 4.0.0 available which supports python 3. So I thought I'll give collective.recipe.supervisor some love to support python 3 too ... or are there any better plans of deploying a zeo setup with varnish/haproxy ?
I have used today supervisor 4.0.0 and collective.recipe.supervisor 0.20 in a python3 buildout with Plone 5.2rc2 to prepare a site for a customer and they work perfectly without needing any change.
Am I getting the same as codeDev if I use the 5.2rc1-uni-installer? Sorry I did not see/read Kim's last line. I updated my versions.cfg and pulled in 5rc2 my bad duhh.
If things go well, I'll try testing cipher.encryptingstorage at some point as I'm using that with a project that requires secure data.
fwiw, encryptingstorage seems to work fine so far.