commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Vernum <>
Subject RE: [GUMP] how to point the finger?
Date Thu, 02 May 2002 04:09:22 GMT

From: Ovidiu Predescu []

> 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 an email notification containing

> Would it be possible to have a similar setup for GUMP? 

In my mind it might not be the right way to go.

It could be helpful that if GUMP fails to build a module it also 
generates a list of changes since the last successful build (so you
can know what was done), but there are two issues.

1] As Lakta has recently seen, the change might be inside a dependency.
Do you list every change to Xerces/Ant/?? also?

2] The project is owned by the community of developers.
While each person should be responsible for making sure their changes
don't break the build, it is the responsibility of all the developers
to make sure the module is correct.
That's why people get CVS commit mails.

It is easiest if the person who made the change goes in and fixes it,
because they know what they've done, (hence having a list of changes
will come in handy) but there is the risk that too much finger 
pointing will reduce the community-ownership of the project.

Just an alternative viewpoint.


This e-mail and any attachments are confidential and may contain copyright material of Macquarie
Bank or third parties. If you are not the intended recipient of this email you should not
read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and
should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any
emails or any attached files. The views or opinions expressed are the author's own and may
not reflect the views or opinions of Macquarie Bank. 

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message