[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Which unresolved bugs block a release?

Kevin Fenzi wrote:
On Thu, 22 Mar 2007 14:23:19 -0400
wwoods redhat com (Will Woods) wrote:

On Thu, 2007-03-22 at 13:07 -0500, Josh Boyer wrote:
On Thu, 2007-03-22 at 19:00 +0100, Hans de Goede wrote:


Most likely a lot of 1) bugs are already solved but never got
closed / retested, others should be taken upstream (and thus
closed in Fedora BZ), etc.
If a lot of 1) bugs are already solved, anyone within the
'fedorabugs' group can act as a proxy to close them out.  Team
effort would be a very good thing I think.
Well then - let's start friday Bug Days again. This friday (and
possibly next friday) we can try to work through the FC5 and FC6 test
release bugs. It's only 380 bugs! Here's the link:


That's (currently) 460 ASSIGNED, MODIFIED, NEEDINFO and NEW bugs
against all the FC5 and FC6 test releases.

Sounds like a good idea to me. I would be happy to help.

What time?
I'll be available from 8u00 (CET / GMT +1) till 17u00 and maybe sometime in the evening too.

> Coordinate on #fedora-devel irc?

Is there more info for people who would like to help?

Good question, for example what should we do with bugs like:
Assigned by reporter to reporter, no valid summary / description, most likely caused by a messed up install, invalid component. Slam close?

Next week: FC5, or FC6?

Possibly. ;)

I say start with the newest bugs first, those contain much more low hanging fruit, so I "vote" to work on this list coming friday:

If this is a weekly thing I would also like to see trying to help out
some of the packages that just have way too many bugs for any single
mantainer to deal with... rpm, kernel, etc.

kernel is very hard to help with (I've written and maintain some kernel drivers, and I'm lost in there). Helping rpm starts with getting rpm an active maintainer, I've filed and watched many rpm bugs and comments to the by pnasrat (the current maintainer) are very scarce. I think that choosing one package and then working on it is a good idea, but again low hanging fruit. For example ImagaMagick has quite a few bugs which should be fixable.

Also an important question to ask ourselves is triage or fixing or both? I'm quite good at debugging C-code (no race conditions please), and have already fixed quite a few bugs. Now if we could combine a few triagers with a few fixers on friday, that might work very well.

This might be a good time to mention the recently-created

Another list? :( Is that really needed? or couldn't discussions take
place here?

+1 +1 +1

Further discussion of this topic should go there.

ok. I will after this I suppose.

Please don't, -ETOOMANYLISTS.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]