[ On Friday, July 13, 2001 at 10:39:25 (-0400), Noel L Yap wrote: ]
> Subject: RE: How well does CVS handle other types of data?
>
> I don't see how any system (let alone tools) can ever absolutely guarantee no
> bugs. If it can, then it might as well guarantee no security holes.
Aegis doesn't guarantee no bugs. It simply requires a new test for
every change and re-runs all the old tests, as well as the new test, on
the submitted new code before it can become the baseline.
If the rest of your process is "working" then no bugs will ever be
re-introduced. If the change is a bug fix then the one more bug will be
squashed and it can never be re-introduced either.
All of this obviously hinges on having a well defined implementation
specification before you even begin coding, of course, as otherwise you
won't be able to write successfull tests that don't break your ability
to create a final proper implementation.
> This is one way to do it. Some would use a version control tool.
I AM USING A VERSION CONTROL TOOL! I'm just using it one step removed
by putting the configuration specification into a "script" that's
version controlled!
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
