[Vxl-maintainers] Being more active in dashboard quality

[Amitha P. <pe...@cs...>]

Folks,

I think we all need to be more active in ensuring that the builds
dashboard is useful. Every so often, something goes wrong and there
are broken build emails sent that are not caused by a code
change. The cause may be the dashboard scripts failing, or by one of
the submitting build configurations going bad, or some other
cause. It is important that we fix these as soon as it is
noticed. This implies that whoever notices it should alert
someone. One central point of contact is this list.

If you did not commit anything the day before, you should not receive
an email about a broken build. If you do, something is wrong. Alert
the list!

If you did commit something and receive and email, look at the error
message. If the error is unrelated to your change, and someone else
has also committed something that may have caused the problem, ignore
it. Otherwise, if the error is something that you cannot correct, do
not understand, or need help correcting, alert the list!

Any comments on the whole dashboard, the broken build emails, and so
on? We should continue to keep VXL multi-platform and multi-compiler,
but should strive to make the process as unobtrusive as possible.

Amitha.