On Tue, Nov 04, 2003 at 02:31:40PM -0700, Lucas Albers wrote: > > Warren Togami wrote: > > I would further suggest our policy include two additional clarifications: > > > > * If we must fix bugs which are not security-related, fix the > > high priority items that cause work stoppage, data loss, etc. > > Don't fix unimportant bugs (simple cosmetic items, rarely used > > features, etc). Let those be fixed in newer Fedora releases. > > * Don't add new features no matter how popular they are, unless > > they are necessary to resolve security or high-priority > > functionality bugs. Good. > If it's a bug and no one encounters it, who cares. The ones who _will_ hit the bug because it has not been fixed. http://c2.com/cgi/wiki?IfItIsWorkingDontChange The stupid "IfItAintBrokeDontFixIt" is mostly an antipattern. Maintenance is a good thing. But stable version of a product indeed do not neccessarily need new features. These are two different things. Not a flame or anything, just rephrasing. -- The most common error message we got from a modula II compiler that I used at an other company was "Unexpected ';', expecting ';'" -- Rick Clements
