Subject: Re: zope29 components
To: None <email@example.com>
From: Takahiro Kambe <firstname.lastname@example.org>
Date: 10/13/2006 00:07:33
In message <email@example.com>
on Thu, 12 Oct 2006 08:23:35 -0600,
Brook Milligan <firstname.lastname@example.org> wrote:
> > And Zope 2.2.x, 2.6.x, 2.9.x aren't completely upper compatible.
> > So, it should better that make zope product packages support these
> > multiple versions of Zope.
> Are the packages compatible with, for example, all the zope 2.*
> versions? Or must there be a specific version of each package, one
> per underlying zope version?
It isn't direct answer for your question, here is a matrix Python,
Plone, Zope and ZODB's release.
Plone Zope Python ZODB
2.0.5 2.7.0-2.7.9 2.3.4-2.3.5 3.2
2.1.3 2.7.0-2.7.9 2.3.4-2.3.5 3.2
2.1.3 2.8.0-2.8.8 2.3.4-2.3.5 3.4 (MVCC)
2.5.0 2.8.7- 2.3.4-2.3.5 3.4 (MVCC)
2.5.0 2.9.3- 2.4.2-2.4.3 3.6 (MVCC)
* Quoted from http://zope.jp/documents/faq/pythno-zope-plone-versions
(written in Japanese).
* ZODB = Zope Object Database, component of Zope.
* MVCC = multi-version concurrency control
And there are more products which runs on Plone or Zope, and they
might depends on specific series of Plone or Zope.
(About relation between Zope 2.x and Zope 3.x, this figure might be
> > (I think that Zope packages should be made some restructuring.)
> Do you have any specific suggestions?
No concrete model at now, but I want to work on...
Takahiro Kambe <email@example.com>