About Me
Hi, I'm Angie, and I'm a geek. If you want to know more, read all the boring details.
- My crazy travel schedule has me located
- HOME until Drupalcon Szeged!
- Currently watching
- Battlestar Galactica - Season 2
- Currently playing
- Final Fantasy VII: Crisis Core
- Currently reading
- The End of Poverty: Economic Possibilities for Our Time
I'm always up for suggestions, too. :)
Drupal powers this site, and I help power Drupal.

Recent comments
- Still Learning Drupal
3 days 14 hours ago - Belgian pralines for the ultimate tester
4 days 4 hours ago - How does one get nominated
5 days 1 hour ago - Thank you
1 week 2 days ago - This is great
1 week 3 days ago - Well, jeeeez, if someone had
1 week 3 days ago - Advanced psychology
1 week 3 days ago - Nice.
1 week 4 days ago - ditto
1 week 4 days ago - Contacted Amber...
1 week 4 days ago

ideally the steps
1. fix all tests
2. testing.drupal.org (or some service) watch cvs commits and upon commit, run tests
3. if testing.drupal.org reports a test failing, someone would roll-back the commit
until it's resolved.
It's really the only fair and sane way IMHO to stay ontop of this. But there is a long way to go to get
there i understand.
It's also important we learn from the failing tests and see if they are failing for good or bad reasons and
if there is something that keeps breaking things over and over that can be fixed once and for all.
Thanks for posting this, you've nailed all the concerns and implications very well!