[Zope] Zope feature freeze project ??

[Julián Muñoz]

So really it is "cheaper" to upgrade the products than to backport the
bugfixes ?

I my mind I have the idea of Debian Potato. Stable for years, bugfixes
backported for years, it is the paradise (for the system administrator)!
Why shouldn't be the experience of Debian Potato valid for Zope ?


Julián



On Mon, 9 Sep 2002, Dieter Maurer wrote:

> =?ISO-8859-1?Q?Juli=E1n_Mu=F1oz?= writes:
>  > ... feature freezed Zope version ...
>  > 3) Tell and explain me why I am wrong.
> I am following the Zope development since 2.1.6 up to Zope 2.5.1
> (usually the CVS branch).
>
> I had no or negligible work with these upgrades with two exceptions:
>
>   *  2 days for Zope 2.1.6 to Zope 2.3.3 (you see, I did not try Zope 2.2=
).
>
>      This was due to dramatic changes with respect to the security policy
>
>   *  1 day for CMF 1.2 to CMF 1.3 (with DCWorkflow)
>
>      This was due to incompatible extensions done by me and
>      Flaurent to DCWorkflow and drastic changes in the
>      way objects are catalogued during copy/move.
>
> All in all, I did not meet your problem.
>
>
> Furthermore, following your idea, you will end up with bugfix releases
> for each major Zope version. Not even companies like Oracle
> (that get big money from support contracts) can do this.
> Even they stop support for older releases...
>
>
> Dieter
>