On 03 May 2002 08:05:59 +0200, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Thu, 02 May 2002, Ovidiu Predescu [EMAIL PROTECTED] wrote:
I think is a good start, but IMO should be integrated not only with
the build process, but also with the automated test frameworks.
All that needs to be
On Wed, 1 May 2002 18:50:40 -0400, Sam Ruby [EMAIL PROTECTED] wrote:
Ovidiu Predescu wrote:
The GCC project uses a very interesting tool for helping point out who
entered a bug in the compiler after doing a change.
...
Would it be possible to have a similar setup for GUMP? I know
Tim,
On Thu, 2 May 2002 14:09:22 +1000 , Tim Vernum [EMAIL PROTECTED] wrote:
From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]]
The tool works by keeping track of who modified the files since the
last build, and what were the changes in the number of regression
tests. If you modify a
On Thu, 02 May 2002, Ovidiu Predescu [EMAIL PROTECTED] wrote:
I think is a good start, but IMO should be integrated not only with
the build process, but also with the automated test frameworks.
All that needs to be done for this is that you make Gump run the tests
as well. Gump already does
Sam,
The GCC project uses a very interesting tool for helping point out who
entered a bug in the compiler after doing a change.
The tool works by keeping track of who modified the files since the
last build, and what were the changes in the number of regression
tests. If you modify a file lets
From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]]
The tool works by keeping track of who modified the files since the
last build, and what were the changes in the number of regression
tests. If you modify a file lets say, that introduces a regression in
the automated tests, you will receive
