linux-kernel - Re: maturity and status and attributes, oh my!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0709010548200.29584@localhost.localdomain>
Date:	Sat, 1 Sep 2007 05:54:14 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: maturity and status and attributes, oh my!

On Sat, 1 Sep 2007, Stefan Richter wrote:

> Robert P. J. Day wrote:
> > given the possible interpretations of EXPERIMENTAL that i hadn't
> > considered until now, maybe it really *does* make sense to tag
> > something as both EXPERIMENTAL and, say, DEPRECATED (does it?).
>
> In theory maybe, for communication purposes perhaps rather not.
>
> The reasoning why a feature is deprecated will typically include the
> gotchas which caused the feature to be considered experimental, if
> such gotchas still apply.

fair enough. there may be times when people won't agree when something
is actually "deprecated."  but in cases of actual disagreement, the
easiest solution is to do nothing -- leave that feature untagged, it
won't hurt anything.  it would be like arguing about whether something
should currently depend on EXPERIMENTAL.  who cares?  a user can
simply click on whether they want to see EXPERIMENTAL stuff, anyway.

the places where this makes sense is where everyone agrees that
something is now officially deprecated -- like when it gets its own
entry in the features removal file with a scheduled removal date.
once that happens, it's beyond the point of debate.

but so what if something gets mis-classified every so often?  you
always have the ability to ignore all that attribute classification in
the end, anyway.  no harm, no foul.

rday

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/