Re: [Zope-Checkins] SVN: Zope/trunk/ - Applied patch for
On Thu, Mar 17, 2005 at 10:34:10AM -0500, Tim Peters wrote:
[Sidnei da Silva] ....
Humm... we are trying to push a Zope 2.8 beta out, do you have or know of plans to use ZODB 3.4 with Zope 2.8?
Yes. Jim needs to fix ZClasses for 2.8 too. ZODB 3.4 requires some Zope(3) features, like zope.interfaces and zope.testing. Jim is adding those on his ZClasses branch. When the ZClasses work is merged (but not before), it becomes possible to move to ZODB 3.4. Zope3 already uses ZODB trunk (3.4 development). We can't afford to maintain a separate ZODB just for Zope 2.8, so view moving to ZODB 3.4 as a requirement for Zope 2.8.
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), 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. For instance, there is no ZODB 3.4 release yet; how much work would that entail? Regards, Martijn
[Martijn Faassen]
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.
participants (2)
-
faassen＠infrae.com -
Tim Peters