That need to close bugs?
mah at jump-ing.de
Fri Sep 21 08:09:01 UTC 2007
Am 20.09.2007 um 12:57 schrieb Aaron Whitehouse:
> Do we really gain anything by having a dev look at "Ubuntu doesn't
> work" every day for the rest of all time?
If the dev has to look at the unchanged bug each day, there's
something wrong with filtering/sorting tools.
> My underlying point is that we all want Ubuntu to be bug-free. It
> isn't and it isn't likely to be any time soon. While it isn't, we need
> to focus our resources on things that are ready to be fixed.
Sure. Perhaps the root of the discussion is, many people understand a
lot of open bugs equals a lot of adminstrative work. I don't see a
I'm no dev but an occasional commiter (to several OSs, including
fixes) and my understanding is, devs' typical administrative work is
to have a look at freshly commited bugs and at those with new info
commited. No need to bother even a second with longstanding
unchanged, but open bugs.
> There is nothing to stop having people trying to complete
> INCOMPLETE bugs by
> asking questions, but confirmed, complete reports need to be the
Sounds a lot like Torvalds' "contents != files", leading to the
development of git. If you want complete bugs to have priority,
please don't try to blame commiters or grandmothers or numbers
overwhelmig your imagination, but give priority to these bugs. Make
sure they appear on top of the bug list in your favourite bug
handling tool and make sure you don't have to waste time with
How about a priority point score system?
+ 50 points on initial commit
+ 50 points on subsequent commit by non-developer (means activity)
+ 50 points on duplicate found / merged in
- 1 point each day
This way, you can focus on what's urgent but don't have to make
people feeling bad by closing / ignoring their commitments.
> A big thanks to all the people keeping the bug system going.
Add my thanks as well.
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
More information about the Ubuntu-devel-discuss