Skip to Main Content
Program Management for Open Source Projects
book

Program Management for Open Source Projects

by Ben Cotton
July 2022
Intermediate to advanced content levelIntermediate to advanced
192 pages
5h 27m
English
Pragmatic Bookshelf
Content preview from Program Management for Open Source Projects

Close Bugs

Problem: Bug reports remain open indefinitely. Some of them are old enough to drive a car.

In a perfect world, all of your bug reports will be closed because they were fixed. That doesn’t actually happen. Even if you can fix every bug, not all of the reports you get will be valid. You need a way to handle invalid reports and the bugs you just can’t (or won’t) fix.

Closure Types

Problem: No one can tell at a glance what it means when a bug report is closed. Was it fixed?

Before we figure out the process for closing bug reports, we should decide on what closure means. At the most basic level, you can simply have bug reports be open or closed. But that doesn’t convey much information to people who may look at the bugs later. And it makes ...

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.
Start your free trial

You might also like

Open Source Projects - Beyond Code

Open Source Projects - Beyond Code

John Mertic
Continuous API Management, 2nd Edition

Continuous API Management, 2nd Edition

Mehdi Medjaoui, Erik Wilde, Ronnie Mitra, Mike Amundsen

Publisher Resources

ISBN: 9781680509939Errata Page