-----BEGIN PGP SIGNED MESSAGE-----
On 12/20/2012 10:21 AM, Marius Gedminas wrote:
> On Thu, Dec 20, 2012 at 05:13:37PM +0200, Marius Gedminas wrote:
>> On Wed, Dec 19, 2012 at 02:42:35PM -0500, Tres Seaver wrote:
>>> On 12/19/2012 01:57 PM, Marius Gedminas wrote:
>>>> Would it be possible to release zope.security 4.0.0 any time
>>>> soonish? Then new buildouts would get new zope.proxy and new
>>>> zope.security, while old buildouts would happily continue to use
>>>> old ones.
>>> I had hoped that the 4.0.0 marker would signal Py3k compatibilty,
>>> but don't have gumption to finish that port today.
>> Whoops. I think I accidentally stepped on your toes by releasing
>> zope.pagetemplate 4.0.0 without first checking if the Py3k port was
>> complete. I just assumed it was, after noticing the 4.0.0 version
>> number in CHANGES.txt.
> I added a tox.ini and 'setup.py test' support to zope.pagetemplate
> trunk and saw that Py3k porting is blocked by zope.security not
> working with Py3k yet.
> No pressure ;-)
>>> Maybe a 3.9.0 release, made by branching from 3.8.3 and just
>>> bumping the zope.proxy dependency?
>> That sounds reasonable.
> Call that a +0.5 vote, because I don't trust my judgment.
I'm actually thinking tat a 3.8.4 release (only tightening the zope.proxy
requirement) would be even better: there are no new features, nor BBB
issues for consumers of zope.security, as a 3.9.0 release might signal.
I will push it out shortly.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -