[Xapian-discuss] Deprecation policy question

[Alexander Lind]

I agree. With a relatively small group of developers, I think you should 
pick the option that minimizes maintenance work and maximizes the time 
you can spend on developing new features.
Keeping their code up to date and compatible with the latest xapian code 
is not much to ask from users, I think.
And if users don't always have time to update their code when the API 
changes they can always hold off with upgrading xapian.

Alec

Kevin Duraj wrote:
> I vote for option (1.)
>
> I do not like option (2.) ... reasons:  it creates more overhead in
> development of Xapian code, red tape that increases maintenance of the
> code to keep long tracking of depreciate code.
>
> Once code is depreciated and replaced with better methods remove it!
> Do not care about users that cannot keep up with changes. We must make
> sure that we advanced with Xapian code as fast as possible.
>
> Cheers
> Kevin Duraj
> http://MyHealthcare.com
> Los Angeles, California
>
>
> On 9/25/07, James Aylett <james-xapian at tartarus.org> wrote:
>   
>> On Mon, Sep 24, 2007 at 05:55:18PM +0100, Richard Boulton wrote:
>>
>>     
>>> The downside is that it becomes less clear when it's okay to break the
>>> ABI and API.  Using major releases to denote that is an option, but
>>> means we'll probably have about 1 major release a year, which somehow
>>> seems wrong.
>>>       
>> Hmm, yeah. My view here:
>>
>>  * breaking the ABI can be done at minors; since there will now be a
>>   /reasonable/ chance that a minor will deprecate something, you
>>   probably need to do code changes to keep perfectly up to date, so
>>   recompiling isn't really an issue
>>
>>  * breaking the API can be done at majors; it's possible we could do
>>   it exceptionally at minors, by concensus on the list where we know
>>   that the number of impacted users is low, and the negative impact
>>   is considerably less than the net gain -- however it's easier to
>>   just break the API only at majors (not counting deprecations)
>>
>>  * breaking the db format should (a) only be done at majors, (b)
>>   hopefully won't happen again anyway ;-)
>>
>> J
>>
>> --
>> /--------------------------------------------------------------------------\
>>  James Aylett                                                  xapian.org
>>  james at tartarus.org                               uncertaintydivision.org
>>
>> _______________________________________________
>> Xapian-discuss mailing list
>> Xapian-discuss at lists.xapian.org
>> http://lists.xapian.org/mailman/listinfo/xapian-discuss
>>
>>     
>
>
>