Hi Martin,
as one of the "2nd wave of Zope3-guys" (which means my
business is app development/maintaining in a day2day-Job,
not developing the core) I assure you that the Z3-Ship
is in safe waters since autumn 2005 - the 3.2 release.
Since I work with Plone 2.1 AND Zope3.2 (for different projects
Chris McDonough wrote:
>> I'm told that the ZODB is the de-facto way of storing content. Maybe
>> soon the default may be a filesystem. Mmm...
>
>
> My feelings are that there should be a "classic" Zope 3 release which
> is exactly what exists now (it should make the assumption that ZODB is
>
> things. Extreme example: In Plone the core Plone product is called
> CMFPlone. It pisses Alexander off. Should we rename it 'Plone' and thus
> break every product that ever imported from CMFPlone? Should we make a
> jungle of aliases and deprecation warnings? Or should we live with our
> mistakes
Forward compatibility is a myth, it doesn't exist.
I would tend to agree. However, the degree of compatability and the time
spans in questions are under the development team's control. It may, at
some point, become more important to ensure continuity than to perfect
things. Extreme examp
