New deprecation procedure

Pedro Alves
2014-09-10T18:59:30Z

On 09/10/2014 05:35 PM, Ulrich Weigand wrote:
> Joel Brobecker wrote:
>
>> So let's discuss the new obsoleting procedure, so we can document it:
>>
>> . I think that the first 4 steps (post email on gdb@, wait a week,
>> then on gdb-announce, wait another week) are fine. Anyone thinks
>> we should go straight to gdb-announce?
>>
>> My thinking is that people interested in maintaining a port
>> with enough skills to do so are likely to already be on gdb@,
>> so we can avoid sending an extra mail to gdb-announce. But
>> the traffic on gdb-announce being very low, and the frequency
>> at which we deprecate targets being fairly small as well,
>> I wouldn't object to a simpler procedure where we email
>> gdb-announce directly.
>>
>> . Remove steps 5 & 6 that mark the code as obsolete, only keeping
>> the last test, which removes the code. I'd add a note to add
>> a NEWS entry.
>
> Sounds all good to me.

To me too.

Thanks,
Pedro Alves