I often come across a bug report and decide that I want to do something once it's fixed:
- Once bug X is fixed, tweet joyfully.
- Once bug X is fixed, update some documentation.
- Once bug X is fixed, add a feature to a fuzzer.
- Once bug X is fixed, retest a fuzz testcase that I assumed triggered bug X but might in fact trigger a different bug.
- Once bug X is fixed, add a regression test for bug W.
- Once bug X is fixed, see if it also fixed bug Y.
I could CC myself to the bug, but then I'll get lots of email and might forget my reason for being CCed. I could create a dependency, but that sends everyone else confusing bugspam and gives me notifications that are easy to miss.
The after-fix tool
I created a tool called after-fix to track these bug-dependent tasks for me. I have a large after-fix config file with entries like:
# Make use of new GC APIs in DOM fuzzer bug 661469
I'll see my note the next time I run after-fix after bug 661469 is fixed.
I've also been using after-fix to ensure workarounds don't outlive their purpose: