DEVELOPER ONLY vs. EXPERIMENTAL in Kconfigs

[Steve French]

Which is the preferred configure option for early experimental code -
"DEVELOPER ONLY" or "EXPERIMENTAL"  ?

After successful testing at the Storage Developer Conference last
week, I am trying to clean up the smb2 (network file system) config
files and had a question about marking an option as "DEVELOPER ONLY"
in Kconfig.  The smb2 file system mounts, does basic file operations,
but has enough known bugs that I would lean toward marking it
"DEVELOPER ONLY" initially, as NFS client did with NFSv4.1 support at
first - but I don't see other components using "DEVELOPER ONLY" (and
"DEVELOPER" for some component seems to mean something different  -
like tools that developers might use instead of "code that is mainly
intended for developers working on network file systems and Samba but
not for general users yet").  Is "DEVELOPER ONLY" or "EXPERIMENTAL"
preferred?

Jeff Layton and I discussed creating a "fs/cifs_common" directory to
move shared code into (perhaps as much as 25% of the code eventually)
for smb2 and cifs, and getting the smb2 code checked in, will help
make this transition faster.   Even though the smb2 and cifs network
file system protocols are quite different (and smb2 is simpler), there
is some overlap in areas such as connection establishment, and
security which will benefit from the move into cifs_common, and
getting the smb2 code in (as either "DEVELOPER ONLY" or "EXPERIMENTAL"
will help).

-- 
Thanks,

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