On 5/19/09 11:06 AM, Martijn Faassen wrote:
> Chris McDonough wrote:
> [snip]
>> Er, it actually isn't a major release. None of *its* interfaces moved. I
>> thought we were defining "major release" as "API change".
>
> Hm, a dependency change isn't a bugfix either.
>
> It's an edge case, and one
Chris McDonough wrote:
[snip]
> Er, it actually isn't a major release. None of *its* interfaces moved. I
> thought we were defining "major release" as "API change".
Hm, a dependency change isn't a bugfix either.
It's an edge case, and one where I think we should err on the side of
caution. It
On 5/19/09 6:49 AM, Martijn Faassen wrote:
> Chris McDonough wrote:
>> On 5/18/09 6:42 AM, Martijn Faassen wrote:
>>> Chris McDonough wrote:
I don't currently have access to publish zope.intid, but I think it's
probably
ready for a release too, BTW.
>>> I just gave you access to thi
Chris McDonough wrote:
> On 5/18/09 6:42 AM, Martijn Faassen wrote:
>> Chris McDonough wrote:
>>> I don't currently have access to publish zope.intid, but I think it's
>>> probably
>>> ready for a release too, BTW.
>> I just gave you access to this package. Stephan has a script by the way
>> that
On 5/18/09 6:42 AM, Martijn Faassen wrote:
> Chris McDonough wrote:
>> I don't currently have access to publish zope.intid, but I think it's
>> probably
>> ready for a release too, BTW.
>
> I just gave you access to this package. Stephan has a script by the way
> that can give you access to a wide
Chris McDonough wrote:
> I don't currently have access to publish zope.intid, but I think it's
> probably
> ready for a release too, BTW.
I just gave you access to this package. Stephan has a script by the way
that can give you access to a wide range of packages, might be a good
idea if he ran
I don't currently have access to publish zope.intid, but I think it's probably
ready for a release too, BTW.
- C
On 5/17/09 1:34 PM, Martijn Faassen wrote:
> Chris McDonough wrote:
>
>> These branches were merged. I made a new release of zope.lifecycleevent
>> (3.5.2)
>> to PyPI.
>
> Thanks ve
Chris McDonough wrote:
> These branches were merged. I made a new release of zope.lifecycleevent
> (3.5.2)
> to PyPI.
Thanks very much for doing this work.
As a reminder for the future, please do release changes in the API (as
in zope.lifecycleevent) as major releases (i.e. 3.6).
I realiz
On 5/15/09 7:33 AM, Martijn Faassen wrote:
> Hanno Schlichting wrote:
>> Chris McDonough wrote:
>>> I've created two codependent branches of zope.container and
>>> zope.lifecyclevent:
>> [...]
>>
>>> I don't know if merging this stuff is reasonable. I do understand the
>>> difference between "lif
Hanno Schlichting wrote:
> Chris McDonough wrote:
>> I've created two codependent branches of zope.container and
>> zope.lifecyclevent:
>
> [...]
>
>> I don't know if merging this stuff is reasonable. I do understand the
>> difference between "lifecycle events" and "container events" and the e
Chris McDonough wrote:
> I've created two codependent branches of zope.container and
> zope.lifecyclevent:
[...]
> I don't know if merging this stuff is reasonable. I do understand the
> difference between "lifecycle events" and "container events" and the events I
> moved out are definitely c
11 matches
Mail list logo
