Why would anyone want to see test failures if they are not developers ? I assume most people monitor
things to get things fixed, so need therefor probably need to monitor commits already.
For the mailinglist :
Start a vote and send the result to the PMC and assuming it is not veto'd, file an issues in JIRA
for infrastructure (preferrably with a link to the vote result).
Mvgr,
Martin
David W. Van Couvering wrote:
I'm amenable to setting up a new mailing list. I wouldn't want it sent
to just derby-commits, I think there may be a set of folks who want to
see test results but not all the commits.
I can own setting up the mailing list -- can anyone tell me how this is
done?
David
Daniel John Debrunner wrote:
David W. Van Couvering wrote:
Hi, everyone. Regarding keeping derbyall clean, I think there are a two
parts to this.
AWARENESS
It is important for us to be aware of the current state of affairs.
Having a web site with test results is necessary for this but, in my
opinion, not sufficient.
In order to increase awareness, I am proposing that an email is sent to
derby-dev after each tinderbox and nightly test run sending out the test
results.
There are a couple of different options here:
1) Test results are sent to derby-commits
2) A new mailing list is set up, something like derby-test-results
These are more of an opt-in option for test results.
Just a reminder that these test results are a great service provided by
Sun Microsystems, not any official ASF testing facility.
If we have others performing a similar service (e.g. I know IBM is
planning to have another test web-site with IBM's nightly results) then
we could end up with many test result messages per day.
Of course if Sun, IBM or anyone else wants to send their test result
messages to derby-dev I'm not sure anyone can stop them.
Dan.
(disclaimer - working for IBM).
