On 11/30/09 13:43 , Hanno Schlichting wrote: > On Mon, Nov 30, 2009 at 1:21 PM, Martin Aspeli<optilude+li...@gmail.com> > wrote: >> Martijn Faassen wrote: >>> This implies we don't want to release zope.component 4.0 for a long time >>> yet. >> >> I think the answer should be "never". :) > > I think never is a rather long time. I'd suggest we think about these > changes more in the timeline of years. > > Looking at Python itself or Zope's own former deprecation policies, it > seems that policies where we deprecate / warn about API changes in one > release and change behavior it one or two releases after that seem to > work. They do rely on their being something like a coherent release of > some language / framework / toolkit though. And they rely on these > releases being made at an interval of at minimum a year or preferably > 18 months (as in Python's case). > > I think that once we get a ZTK 1.0 release out that promises to be > maintained for at least three years, we can start working on a ZTK 2.0 > which introduces deprecation warnings about the changed behavior and a > 3.0 that will change the default. If released at an interval of 18 > months like Python, that puts these changes about 3 years into the > future with a lot of time in between to adjust.
We could also say that we will clean up the API when we move to Python 3. That is a natural breaking point anyway, so it will not any extra pain for users of the ZCA. Wichert. _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )