Set Release Criteria
Problem: You don’t know when the release is ready to ship.
If you’re waiting until all of the (known) bugs are fixed before you ship the release, you’re going to need a very comfortable chair. The only way to produce meaningful software without any (known) bugs is to avoid testing. Since that seems like a recipe for disaster, we have to come up with another approach. Let’s figure out which bugs are acceptable and which aren’t.
We can start by turning to our bug tracker and looking at all of the bugs in the prerelease version. For each one, we ask ourselves “is it okay to ship the release with this bug?” This involves a few difficulties. First, debating each bug will take a long time. Not everyone will agree on whether the ...
Get Program Management for Open Source Projects now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
