[Zope-Coders] Upcoming releases

[Tim Peters]

[Chris McDonough]
...
> Also, FWIW, Tim is on vacation

This is true, although it's hard to tell that with me typing here <wink>.

> and ZODB in 2.8 is in an unknown state (it's not linked in any automated
> way to the ZODB 3.3 that Zope 3 is using,

None of ZODB, ZConfig, or zdaemon are linked in any automated way to
any version of Zope under SVN.  Zope trunk ("2.8"), Zope3 trunk, and
Zope X3 branch each have their own distinct copies of ZODB, ZConfig,
and zdaemon.  Checking in from one copy has no effect on any other
copy.  For that matter, the ZODB trunk and branch each have their own
distinct copies of ZConfig and zdaemon too.  The CVS setup was
night-and-day different here, where a checkin from any checkout was
instantly seen by all clients.  There are good and bad points for both
ways of doing it.

The unique thing about Zope trunk right now is that it doesn't *look*
like the job of stitching (*a* copy of) SVN ZODB into it was left in a
wholly sane state.

> so someone needs to do that merge).

Yes.  Perhaps for ZConfig and zdaemon too.

> It is probably a year old or so, maybe.

I don't think it's *that* bad.  It looks like Zope trunk has ZODB3 as
of the day Jim first converted CVS to SVN, plus a random checkin made
to ZODB/component.xml that should not have been made from a Zope
checkout, plus some aborted old attempt to try to update ZODB to an
early 3.3 alpha state.

I *expect* this will be easy to repair, if I can get bandwidth from
Jim to clarify how he originally stitched ZODB into Zope trunk (it's a
multi-step process, essentially copying one ZODB directory at a time
into a different place in the Zope trunk; one of the things I don't
know is exactly which set of ZODB directories he copied, and it
doesn't appear to be the same set as got copied into Zope3/ZopeX3).