[ZODB-Dev] RE: ZODB 3.2.5c1 internal release

[Tim Peters]

[Andreas Jung]
> Releasing 2.7.4 by omorrow was my first plan but because of personal
> plannings I had to make the release otherwise I would not have too much
> time over the next days resulting in a further...

That's OK -- it's better to have something released than nothing <wink>.

> and I was not aware that you were working on this release. I think we
> must improve our coordination.

I've asked before that I get a couple days notice before any release.
That's all that's needed.  Because of the way CVS is set up, it's impossible
to change any code on the Zope-2_7-branch branch of the ZODB3 module without
also changing it on the Zope-2_7-branch branch of the Zope module.  So, in
effect, I'm *always* working on the next Zope 2.7 release (even if I don't
intend to).

>> Collector 1503:  excessive logging. ...

> This request came from Dieter

Right.

> and I am sure that we can backport this fix to our company Zope CVS if
> necessary. So if this is the only change I am fine with releasing ZODB
> 3.2.5 final with Zope 2.7.5.

Assuming you meant Zope 2.7.4, good, because it's already checked in to the
Zope-2_7-branch of the ZODB3 module, so necessarily also shows up in a
Zope-2_7-branch checkout of Zope now.  Of course I believed it was an
extraordinarily safe change, or I wouldn't have checked it in now.