On Jul 10, 2006, at 3:38 PM, David Blevins wrote:
On Jul 10, 2006, at 11:19 AM, Kevan Miller wrote:
On Jul 10, 2006, at 1:55 PM, David Blevins wrote:
Kevan, you've been tck dog for six months now. Having built the
system and done the job myself, I know you're not going to
survive another six months. We definitely need to get someone
else to take that job for a while.
I certainly agree with that... I would also hope that we can work
on distributing the burden, a bit.
[...]
I see the following pieces:
3) Monitoring/advertising test results.
You have any ideas on what we can do raise awareness of what is
going on with our tck status, or track what's not being worked on?
Some sort of jira reporting system (as Alan mentioned) would be
useful for tracking problems. The GBuild summary reports certainly
help out a lot. Biggest problem is probably getting from the report
to having enough data to start categorizing/diagnosing the problem.
--kevan
Hey all you committers, any suggestions? Do you actually peek at
the results on a regular basis? If not, do you have any
suggestions on what would be the best way to communicate TCK status?
-David
