At 03:46 PM 12/7/2005 -0500, Mike Taylor wrote:
Ok, let me try and summarize so we can focus on what is needed to solve
the different issues raised:
- we need to add email notifications to the tinderbox build/test failed
event
- we need to add SVN commit information to the tinderbox status page
and notifications
- we need to make it easy to either extract or locate the actual point
of failure or error inside the build logs
Did I miss anything?
Naming names. :) I don't think we're going to make any progress on our
organizational issues as long as knowledge of who the "offenders" are
remains private. We can only ponder the mysterious "they" who are breaking
the rules and wonder what all the fuss is about. (While a rotating sheriff
duty would certainly expose more people to the issues, it would not give
them a viable perspective on who the offenders are because of the small and
infrequent time-slicing.)
So, if we are developing systems to enforce the rules, they should inform
us in an automated way as to who is not following them, if the system
cannot itself directly enforce the rule.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
