Re: [Checkins] SVN: zope.dublincore/trunk/ Renamed the ``zope.app.dublincore.*`` permissions to ``zope.dublincore.*`.

Tres Seaver <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jacob Holm wrote:
> Hi Michael, Tres
> 
> I agree a new major version is required due to the new "feature" of
> having new permission names, but there is no reason to break
> compatibility with code using the old names.
> 
> IIRC the <redefinePermission/> zcml-directive  is there exactly to
> provide backwards compatibility when renaming permissions.  Use like:
> 
>   <redefinePermission
>       from = "<no longer defined permisison id>"
>       to = "<existing permission id>"
>       />
> 
> It is defined in zope.security:meta.zcml along with the <permission/>
> directive, so should be usable with any code that uses that.

Thanks for pointing out that directive, whose existence I had forgotten.
 Assuming we put the 'redefinePermssion' directives in place on the
trunk, why shouldn't we leave the version number as is?  I consider the
rename a bugfix, not a feature, and if we make it backwared compatible,
there is no reason to bump the major version.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          [email protected]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvRnlwACgkQ+gerLs4ltQ5etgCg3UwAT0AGU+cu26+bLBbCRBp4
SG0AniEokjNlI9ReKVZu4Htu13wn2CQM
=c0vh
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist  -  [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.