Deprecation period (was Re: [Zope3-dev] BBB and Deprecation Warnings)

Christian Theune ct at gocept.com
Wed Jan 4 05:41:11 EST 2006


Hi,

Am Dienstag, den 03.01.2006, 14:41 -0500 schrieb Jim Fulton:
> > As much as BBB code annoys me personally, I think maintaining a minimum 
> > compatibility window is necessary for an important class of user.
> 
> I think 12 months is a bit short.  I don't think the backward-compatibility code
> is that burdonsome, once written.  What do other folks think?

Based on the argument of Stephan that we might not remember how the
deprecated feature worked, it might be hard to maintain it for a very
long deprecation period. I think it might not be enough to just leave
the code around but we'll have to do something to keep it working (with
the same semantics) in the new version. But this is a case-by-case
issue.

I for myself think 12 months is ok. I wouldn't do a shorter period, but
I won't ask for a longer period. On projects that are stable and work on
a certain version of a platform we stopped upgrading the whole
environment all the time anyway. Even during development.

Cheers,
Christian

-- 
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20060104/c2184ded/attachment.bin


More information about the Zope3-dev mailing list