(ccing wiggy in as a ping as he requested for such issues in #8839)
On 4 Jan 2009, at 03:06, Martin Aspeli wrote:
This is actually really bad, and I think it should block the 3.2 full release (i.e. with installers).
+1
I think we need to: 1) Get a release of Products.NuPlone that works with 3.2 out to PyPI and dist.plone.org immediately. 2) Update the Plone egg to depend on it in a 3.2.1 release. 3) Base the installers and the release announcement on this version.
3a) Remove existing release announcement from prominent places Matt _______________________________________________ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
