Separation of concerns in a bug tracker
[Simon Tatham, 2024-11-01]
Introduction
Some rants
Unified ‘Fix Version’ field
Two-tier Status and Resolution fields
Fake bugs for other kinds of to-do item
Separation of concerns
Facts link to source control; plans link to
time periods
Feature requests are only plans, until they’re
implemented
Each to their own: planners update
plans, developers update facts
Plans table can be weeded while the factual
bug records stay open
Time is accounted to plans, not bugs
You don’t have to have plans at all...
Read more at chiark.greenend.org.uk