[Zope-Coders] Back in town

[Tim Peters]

[Andreas Jung]
> I am back from vacation.

Welcome back!

> Can someone update me about the necessity of 2.7.3 release

"Critical" is quite arguable, but has been covered by others.

> and the status of code on the SVN trunk (for a planned 2.8 released
> this month)?

That one's much harder to judge.  I haven't seen evidence of work done
on the SVN Zope trunk since it was created.

Note that It's very different than the 2.7 CVS setup:  in CVS, the
modules for (at least) ZODB/ZEO, ZConfig, and zdaemon are shared
across checkouts.  So, e.g., when I check something in to a ZODB3
module checkout, it shows up in a Zope module checkout automatically. 
Or if I check it in from a Zope checkout, it shows up in a ZODB3
checkout.  Likewise for (at least) ZConfig and zdaemon.

But in the SVN setup, none of that is true:  Zope has its own,
distinct, *copies* of (at least) ZODB/ZEO, ZConfig and zdaemon, and
checking something in from a checkout of one of those has no effect on
checkouts of any of the others.

So, for example, I'm sure that the SVN Zope trunk still has the copies
of (at least) ZODB/ZEO, ZConfig, and zdaemon as of the day Jim first
set up the SVN Zope trunk, so still suffers from all bugs in those
things that have been fixed since then.

I liked the CVS arrangement better.  As is, it's nobody's official
responsiblity to keep the SVN Zope trunk in synch with the "external"
core code Zope relies on, and a predictable consequence is
"unexpected" integration problems when someone decides to slam in new
copies of these things right before a release.  Indeed, we just went
thru a round of that when slamming a current ZODB/ZEO into the Zope X3
branch for the latter's beta 4 release (it turned out that some of the
X3 tests were relying on accidents of transaction semantics).

In short, life is more brutal on the SVN trunk, and for several reasons.