Re: [PATCH] Remove CONFIG_EXPERIMENTAL

[Dave Jones <davej@redhat.com>]

On Tue, Aug 28, 2012 at 10:10:48AM -0400, Jeff Garzik wrote:
 > On Mon, Aug 27, 2012 at 5:53 PM, Kees Cook <keescook@chromium.org> wrote:
 > > This config item has not carried much meaning for a while now and is
 > > almost always enabled by default. Remove it and adjust various config
 > > logic and documentation.
 > 
 > It does have meaning...  !CONFIG_EXPERIMENTAL means more stable.  In
 > the past things would get CONFIG_EXPERIMENTAL until they've been tried
 > in the field or otherwise hit some goal in the developer's mind.
 > 
 > Is this a practical distinction?  Probably not, as the markers often
 > go unmaintained...

That's exactly the point. We have 'experimental' code that's been marked
as such for 10-15 years. Maturity has nothing to do with that option,
even if that was its original intention.

The reality seems to be that near everyone sets EXPERIMENTAL because
there's so much stuff tucked behind it, that they want at least some of it.
They aren't choosing this option because they care about how mature the
code is, they're setting it because they *need* something that it's hidden behind.

What *might* be a more useful thing, is instead of adding new options
depending on EXPERIMENTAL, introduce something like CONFIG_NEW_IN_3_6
(and a release or so later, when it's not considered new any more,
drop it). But I'm not convinced that even this wouldn't succumb to
the same neglect that EXPERIMENTAL has.

	Dave