[Xapian-discuss] Deprecation policy question

[James Aylett]

On Mon, Sep 24, 2007 at 04:16:41PM +0100, Richard Boulton wrote:

> >[Start the deprecation cycle for an API call at minor releases]
> >>That's roughly what my option 2 suggests, of course.  Except that in 
> >>option 2 we document the features as deprecated straight away.
> >
> >Not just document; putting it into the warnings layer of the API,
> >which I think is a step too far.
> 
> No, option 2 is where we _don't_ put it into the warnings layer of the 
> API (until the next minor release), but do document it as deprecated 
> straight away.

Umm, yeah. Ignore that :)

Hmm. Option 2 feels unclean, but maybe it's better. I don't like the
complexity, though.

> >The thing is that I'm not convinced there's a problem with bumping the
> >minor version when we start a deprecation cycle. I don't see how that
> >can hurt, and it allows everything else to work smoothly.
> 
> I think, in practice, this would simply mean that almost every release 
> was a minor release.

Really? If our API is really that volatile, and will continue to be
so, then I'd argue we have a different problem.

J

-- 
/--------------------------------------------------------------------------\
  James Aylett                                                  xapian.org
  james at tartarus.org                               uncertaintydivision.org