Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.

From: Tilman Schmidt
Date: Tue Feb 20 2007 - 11:29:04 EST

On Sun, 18 Feb 2007 19:35:07 +0100, Bartlomiej Zolnierkiewicz wrote:
> I think that the patch is useful and that the distinction between
> DEPRECATED and OBSOLETE options is quite clear:
> * DEPRECATED == new better code is available, old code scheduled for removal
> * OBSOLETE == no replacement yet but the code is broken by design
> and unreliable, not scheduled for removal yet

Is that really the consensus on these definitions? I thought it was
more or less the opposite:

* DEPRECATED == no (complete) replacement available yet, but it has
been decided that this code is less than optimal and alternatives
should be preferred

* OBSOLETE == replacement available, no reason to use this code anymore

Tilman Schmidt E-Mail: tilman@xxxxxxx
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Attachment: signature.asc
Description: OpenPGP digital signature