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

slightly different workflow
1a. fix all tests
1b. testing.drupal.org fetches RTBC and CNR patches from the queue and marks any that don't apply (~70%) to needs work (in preparation for...)
2. testing.drupal.org fetches all patches from the RTBC and CNR queue, runs them against all tests (and their own if provided), and marks any that break tests to needs work.
3. no need for three, because a patch that breaks tests never stays RTBC for more than a few hours, but run tests on HEAD anyway just in case something slips through 2. Might need a special "don't test this" flag somewhere for particular exceptions.