By this definition, however, the scheduler and virtual memory manager are bugs. So it's not really a useful definition. It would also make feature freezes pointless, since features can be disabled and won't affect everyone, whilst bug fixes should be heavily controled since they affect everyone.
As an exercise to help make Linux development less crazy, coming up with REAL definitions (not trite sayings) and removing the seeming arbitrariness in designation would be nice. Not neccicarily making rigid, unchanging policies, but a guideline that people can write to, and know what to expect from a feature freeze. In 'normal' software development, a feature freeze usually means that APIs don't change, and entirely new filesystems don't appear...
Mike
----------------------------------------------
Michael Zappe <zapman@interlan.net>
Chief Architect, Filesystems
Interlan Communications
111 Corning Drive
Cary, NC 27511
"The sorcerer is a Simple Realist: the world
is real--but then so must consciousness be real
since its effects are so tangible. The dullard
finds even wine tasteless but the sorcerer can be
intoxicated by the mere sight of water."
--Hakim Bey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/