From: Peter V. <pet...@ya...> - 2010-03-10 07:34:35
|
--- Brendan McCane <bre...@gm...> wrote: > Hi Fred, > What you suggest is a good idea, except for two factors: > 1. I tried this previously and it had pretty much no > effect on check in behaviour. > [...] > Wheeler, Frederick W <wh...@ge...> wrote: > [...] That might get people to fix up the dashboard. [...] It's also my impression that the dashboard is not so green as it was until about a year ago. A deadline for a release should *not* make a difference to whether a check-in is compiling or not! I would urge all developers to at least *always* check the dashboard *after* a check-in, and (in case of increasing # errors or warnings) look at them *and immediately check in a fix* if the error (or severe warning) is caused by their check-in! Verifying *before* a check-in is of course much better; that is; recompiling *the whole of* vxl, and not just the file that was changed!!! I've the impression that recently even this kind of verification is not always performed... -- Peter. __________________________________________________ Använder du Yahoo!? Är du trött på spam? Yahoo! E-post har det bästa spamskyddet som finns http://se.mail.yahoo.com |