David Heinemeier Hansson wrote:
I think just emailing this list on breakage is good. Then anyone has a
chance to help fix the bug. If it becomes too spammy, we'll make a
separate list for it.
Thanks for doing this! Now someone working with MS SQL, DB2, and all
the other non-oss adapters please follow suit ;)
Ok, my automated process will go live shortly, just waiting for 1 more
svn checkin to test the last boundary case. My process..
1. Runs every 5 minutes, looks for more recent revisions, and tests them
one at a time (to more easily identify the breaking revision).
2. Emails me and rails-core on breaks, along with the info on the
changeset and the specific unit test failures.
3. On subsequent tests, if the failure is the same, it remains silent;
if the failure gets worse (eg, more output from `rake test_oracle`) or
better, it sends out another email.
4. When it's green again, another note goes out.
It's not a real pretty script, but I'm happy to share it without any
volunteers looking to do something similar for MS SQL, DB2, etc.
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
