Am 19.04.2010 um 22:21 schrieb Tres Seaver:
Log message for revision 111145: Renamed the ``zope.app.dublincore.*`` permissions to ``zope.dublincore.*`.
Applications may need to fix up grants based on the old permissions.
fixes lp:566724
Changed: U zope.dublincore/trunk/CHANGES.txt U zope.dublincore/trunk/src/zope/dublincore/configure.zcml
-=- Modified: zope.dublincore/trunk/CHANGES.txt =============================================================== --- zope.dublincore/trunk/CHANGES.txt 2010-04-19 20:19:54 UTC (rev 111144) +++ zope.dublincore/trunk/CHANGES.txt 2010-04-19 20:21:52 UTC (rev 111145) @@ -5,6 +5,9 @@ 3.6.1 (2010-04-19) ==================
+- Renamed the ``zope.app.dublincore.*`` permissions to ``zope.dublincore.*`. + Applications may need to fix up grants based on the old permissions.
Hi Tres, It's fine to rename these permissions, I like it. But this change is so big that it requires a new major version of this package: it requires changes in other packages, too, as you already said in your log message. Could you please: - unmerge these changes from the 3.6 branch and re-release a new 3.6.3 without the permission renaming, - do a new 3.7.0 release including the renaming and - depend on the 3.7 release in the packages where you updated ftesting.zcml to use the new permissions (zope.app.file and zope.app.container)? Thanks in advance. Yours sincerely, -- Michael Howitz · mh@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development