On Wed, Jul 13, 2005 at 11:09:40AM -0700, Justin Mason wrote: > "masses" is currently under C-T-R for minor changes. I propose that > we do the same for "t", too, since bug 4480 is an example of a trivial > t change that fixes a release-breaking bug, and I'm sure there'll > be more.
masses is fine with me, since users won't actually be impacted by any changes
there. t is a little different, though not as critical as the rest of the
code/rules/etc.
Basically what I'm thinking is that small changes are fine, but large/complex
changes are not. We really ought to be doing "make test" and such before
tagging a release and such, btw, so we don't have "release-breaking" t bugs.
--
Randomly Generated Tagline:
"People who have more power than you do are hard to subvert easily."
- Elizabeth Zwicky at LISA '99
pgpODvSlUQ9Pq.pgp
Description: PGP signature
