Marc Balmer wrote:
Nikolay Sturm wrote:
* Marc Winiger [2008-02-08]:
The versions of zope and plone in the -current cvs tree are broken.
They don't work togheter. So we decided to split the ports into
multiple versions, that the user can choose the version he needs.
Why would it make sense to have multiple versions of both in-tree?
It not only makes sense, it is almost a requirement, for two reasons:
1) Plone usually relies on older Zope Versions, much like Zope usually
relies on older Python Versions. If you want plain Zope, you want the
current version, if you want to run Plone, you usually need an older one.
2) Updating Plone is very hard and sometimes not even possible (Plone
2.0 to Plone 2.1 was such a nightmare). Plone releases are not
compatible. This is one of the cases where upgrading is really, really
painful. So we do not force users of Plone to upgrade every 6 months.
The Plone/Zope combination that currently is in the tree does not work
together. It requires Zope 2.9. And a good Plone would we 2.5, not
2.1. So this is the final step of Zope/Plone cleanup (adding the
python2.4/python2.5 flavours to many python ports has been part of this
cleanup).
Nikolay, do you see the problem we have? Do you have any objections to
the way we solved it?
Is there anybody else interested in working zope/plone version? Any
testing happend?
We have running plone 2.5 instances on zope 2.9, built with this
splitted port. A new bulk-build is running at the moment.
Marc
