Chapter 10Track and Triage Bugs
You don’t want bugs in your project, but all nontrivial software has bugs. And enhancement requests. And instances of not-a-bug-but-it-seems-that-way-to-the-users. So while you might intuitively think that a low bug count is good for your project, that’s not necessarily the case. In Producing Open Source Software [Fog17], Karl Fogel says a higher number of bug reports reflects better on the project because it shows that people use it.
That’s true with a caveat: your bugs can’t be stale. If you have a lot of bugs because you have a lot of users, but the bugs get fixed—or at least looked at—that’s good. It shows your project has an engaged user community and responsive developers. If the bugs sit forever with no ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access