AdoptPackage

Differences between revisions 34 and 35
⇤ ← Revision 34 as of 2007-02-28 18:01:10 →
Size: 4799
Editor: 217-151-110-115
Comment:
← Revision 35 as of 2008-08-04 17:05:10 → ⇥
Size: 4785
Editor: adsl-99-139-209-196
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Adopt-a-Package for bugs is an experimental approach to bug triaging and fixing. Currently, there are different approaches to finding bugs and fixing them. Some people read bug reports as they come in and deal with them in almost real-time. Some people prefer to find the oldest unresolved bugs, or search for untriaged bugs. This approach is a bit different, bugsquad members can choose to focus on a package, and deal with as many bugs in that package as possible. The rationale for this approach is that there are many packages with old bugs that can be rejected or have been solved long ago, where the last comment was filed more than a year ago. It may be a good exercise to go through important packages in Ubuntu that have bugs that has been gathering dust, and to shake them up a bit. Adopt-a-Package is an approach to bug triaging; Currently, there are different approaches to finding bugs and fixing them; Some people prefer to read bug reports as they come in and deal with them as they are reported, others prefer to find the oldest open bugs and work toward the newest.
Line 5: Line 5:
Initially, it might be best for a person to adopt only one package at a time, when they're done with a package, they move on to a new one. Please discuss on the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad Bugsquad mailing list] This approach is a bit different, BugSquad members choose a package to focus on and attempt to triage all the bugs for their chosen package. After all the bugs have been triaged, keeping up with new bugs becomes a relaxed daily process. After a package has been fully triaged, and while triaging a trickle of new bugs for an adopted package, adopt another package and repeat. The rationale for this approach is that this will produce experts within the Bug Squad for any particular package as well as keep the untriaged bugs low for critical packages.

Initially, it would best for a person to adopt only one package at a time, when they're done with a package, they move on to a new one. Please discuss on the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad Bugsquad mailing list.]
Line 8: Line 10:

 * [https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bugs debian-installer]: JonathanCarter, OtherPersons		    
 * [https://bugs.launchpad.net/ubuntu/+source/debian-installer debian-installer]: JonathanCarter, OtherPersons
Line 21: Line 23:
 * [https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bugs acpi-support] 220
 * [https://bugs.launchpad.net/ubuntu/+source/control-center/+bugs control-center] 117
 * [https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bugs debian-installer] 163
 * [https://bugs.launchpad.net/ubuntu/+source/evolution/+bugs evolution] 269
 * [https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs firefox] 607
 * [https://bugs.launchpad.net/ubuntu/+source/gaim/+bugs gaim] 137
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bugs gnome-power-manager] 197
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bugs gnome-system-tools] 130
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bugs gnome-panel] 137
 * [https://bugs.launchpad.net/ubuntu/+source/grub/+bugs grub] 122		  * [https://bugs.launchpad.net/ubuntu/+source/acpi-support acpi-support] 209
 * [https://bugs.launchpad.net/ubuntu/+source/control-center control-center] 61
 * [https://bugs.launchpad.net/ubuntu/+source/debian-installer debian-installer] 175
 * [https://bugs.launchpad.net/ubuntu/+source/evolution evolution] 505
 * [https://bugs.launchpad.net/ubuntu/+source/firefox firefox] 522
 * [https://bugs.launchpad.net/ubuntu/+source/gaim gaim] 157
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager gnome-power-manager] 239
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools gnome-system-tools] 188
 * [https://bugs.launchpad.net/ubuntu/+source/gnome-panel gnome-panel] 167
 * [https://bugs.launchpad.net/ubuntu/+source/grub grub] 186

BugSquad 'Adopt a Package'

Adopt-a-Package is an approach to bug triaging; Currently, there are different approaches to finding bugs and fixing them; Some people prefer to read bug reports as they come in and deal with them as they are reported, others prefer to find the oldest open bugs and work toward the newest.

This approach is a bit different, BugSquad members choose a package to focus on and attempt to triage all the bugs for their chosen package. After all the bugs have been triaged, keeping up with new bugs becomes a relaxed daily process. After a package has been fully triaged, and while triaging a trickle of new bugs for an adopted package, adopt another package and repeat. The rationale for this approach is that this will produce experts within the Bug Squad for any particular package as well as keep the untriaged bugs low for critical packages.

Initially, it would best for a person to adopt only one package at a time, when they're done with a package, they move on to a new one. Please discuss on the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad Bugsquad mailing list.]

Adopted Packages

Packages that need particular care

List packages here that are up for adoption. The application bugnumbers of the bughelper suite is useful for finding out how many bugs a particular package has. Below you will find a list of packages which could use some attention and their quantity of bugs as of 2007-02-14. Don't be intimidated by the number as it is the total count of open bugs not untriaged ones.

Packages that have been 'swept'

CategoryBugSquad CategoryBugSquad

BugSquad/AdoptPackage (last edited 2015-05-12 13:41:48 by 131)