On Tue, 2006-03-14 at 08:34 -0500, Robert Sayre wrote: > On 3/13/06, Michael Bernstein <[EMAIL PROTECTED]> wrote: > > > > Given the non-final status of APP, perhaps it would be better if, rather > > than immediately removing tests, they were marked as 'deprecated' and > > deprecated tests were skipped by default, unless an appropriate command > > Actually, I've been tempted to back the test suite out. If the > MUST-level errors can't point at a section of the spec (or 2616), they > don't belong there. So, why shouldn't it be deleted?
Because deleting it wholesale (rather than, say, commenting it out) makes unnecessary work for someone who wants to fix the test? The point of using version control isn't to ease the making of changes per-se, it's to reduce coordination costs between people making changes. If you really want to make such sweeping changes as deleting all tests wholesale and starting from scratch, it's more appropriate to create a branch than mess with the trunk. - Michael
