--On 14. Juni 2006 07:32:42 +0100 Chris Withers <[EMAIL PROTECTED]> wrote:

Florent Guillaume wrote:
Yes but the deprecation has been there for a while, and the third party
product developers have been ignoring the warning. Their loss.
And this is only for Zope 2.10 which I doubt these third party products
are using at the moment.
If we don't remove things at some point, there's no point in doing
deprecation warnings.

This and things like it have been niggling me for a while now and I guess
this finally prompted me to write a mail on it...

I know the good reasoning behind the time-based releases, but have they
really worked out?

Yes and No.

Yes: It's a must to have Zope 2 and Zope 3 in sync. Zope 2 development got a some more momentum again.. No: Half a yr is a short time. Major changes happened right short before the first beta release. Not all Zope users won't follow this fast release cycle.

For me, the fact that Zope 2.9.3 still emits
deprecation warnings on a fresh install (zLOG...) is a pretty bad sign.

Deprecation warning is only annoying but not a bad sign. Deprecations are not a functional problem.

Now, this could all be seen as fair game, Zope _is_ going through a
period of big and positive change as Zope 2 and Zope 3 converge, things
like zLOG finally get put to rest and we move onto newer more powerful
versions of python.

right...I did not think that we deprecated and removed something without having a reasonable replacement...or did we?

If that's the case, then I hope we, as a community, "get there" at some
point and can get back to focusing on the stability of the good ol' days.

+1, +1, +1


@all developers: I hope you don't forget the bugday tomorrow :-))

Attachment: pgpcyrA2gyahB.pgp
Description: PGP signature

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to