On Wed, 2006-04-10 at 10:26 +0200, Patrick Gerken wrote:
> Notice especially how they mention that a deprecation phase can be days.
> So for me it looks we are actually a bit ahead of the competition, but
> maybe somebody can correct me.


> I think we use Interfaces in Z3 to "publish" Methods. So "maybe" it
> makes sense to have a smaller core API with longer deprecation
> periods, so that standard projects can try to rely on core API with
> long deprecation phase and extender would use the one year deprecation
> phase. But as I said earlier, I think we are quite ahead already.


> But it is not fair to compare the stability of a programming language
> standard modules API with a application framework api. But maybe I am
> not good in searching and somebody points me to the well thought out
> JBoss or Websphere deprecation policy

Thanks for this insight.  As a proponent of sensible deprecation it's
nice to have some evidence rather than simply sputtering, "but but... we
gotta be able to change stuff!"


- Rocky

Rocky Burt
ServerZen Software -- http://www.serverzen.com
News About The Server (blog) -- http://www.serverzen.net

Attachment: signature.asc
Description: This is a digitally signed message part

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