> Oh, also please note that we're merging zope.interfaces and zope.testing
> into Zope 2.8 already. So once we merge that branch (today, we expect),
AFAICT, that didn't land today, at least not on the trunk.
> ZODB 3.4 could be merged in. But I'm worried that there are other
> factors involved with ZODB 3.4 that will hold up release even further.
Even further than what? If you want to maintain ZODB, feel free to
release 2.8 with the random snapshot that's there now <wink>.
Otherwise-- and 3.3.1 or 3.4 --it needs another ZODB first.
> For instance, there is no ZODB 3.4 release yet;
Neither a 3.3.1.
> how much work would that entail?
2-3 days (for both 3.3.1 and a 3.4), but I'm 7 days solid at PyCon
starting tomorrow morning so it won't be the coming week. The week
after could work; I don't yet know what priority my management
attaches to this project relative to other projects on my plate.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -