Hi Seb,
On 04/09/10 10:22 am, Sebastien Lelong wrote:
Buildbot failed again due to last Eur's commit. So far no reply from
Eur. It already happened before, and I did moved his libs & samples in
"casualities".
I can see three different options in order to fix this in the long term:
- removing commit permission to Eur, so next time he'll show here and
ask why he can't commit. We may explain then he has to check buildbot
results (or even better, his code before committing) after a commit. (he
actually knows this, as he was a big fan of buildbot at the first it was
setup)
- setup a buildbot dedicated to Eur, which detects his commits and
automatically move his files to "casualities"
- pick someone here who will fix the code. This can be done through
round robin, randomly, or better, William can handle this. William,
AFAIK, since Eur is your sponsor, as mentioned in libraries and samples
you commit, would you also fix Eur's code ?
Difficult to compare the pro's and con's!
One thing we shouldn't do is making exceptions for one or more specific
persons. In earlier discussions I've indicated that I think it is not
respectful to let 'dirty' code (in the sense of violating the JSG) be
fixed by someone else. So I must vote for number one, but I regret that
this is needed.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
