I volunteer myself to start off the janitor group for bugzilla, to clean up the hundreds of outdated/fixed/invalid bugs that litter bugs.gentoo.org.
reassigning to bug-wranglers, since they're the ones to make this call afaik.
seems to be a really good idea
spanky what do you think about this ?
since this is a one time dealie i'd propose just making a list of bugs that have been messed up, post the list here and we'll go through and close them ... if you use the form 'Bug 100' we'll see when the bug is closed and we can easily see which bugs still need to be closed
"since this is a one time dealie" Yeah right. You honestly don't think that bugs entries in a bugs db of this size don't constantly fall behind?
Just to add a little more substance to the idea: A lot of outdated bugs have become so because the bug owner / assignee / maintainer (pick your favourite) is simply too busy with other things. The idea is to clean 'em up without having to 'bug' them if you'll excuse the pun. There's things like feature requests that are already done, ebuilds that already exist, etc etc. Anyway, I'll post a few here just to give you the idea.
This is just a quick glance at the bugs going up to #3000. Some need flagging as later, some as resolved, some as can't/won't fix. TBH this was probably the worst section for me to look at given that they come at the top of a list and hence are probably reviewed more often than those that are in the middle of the mire. Still, the 'later' flag is hideously underused in this bugzilla. Bug 233 Bug 311 Bug 535 Bug 991 Bug 1186 Bug 1442 Bug 1815 Bug 1925 Bug 1957 Bug 2061 Bug 2272 Bug 2328 Bug 2388 Bug 2391 Bug 2676 Bug 2910
Er that link to 2676 was a typo. Bug 2767 is the right one.
What about: Bug 4315 Bug 4613 Bug 7274 carpaski/dev-portage bugs really need a cleanup what about chadh, is he still active?
Bug 15445 Bug 15453 Bug 16463
chadh isn't active gentoo-dev any more
so we should assign his bugs back to bug-wranglers
Maybe somebody should go through the list of assigned bugs and look which devs aren't active any longer: http://bugs.gentoo.org/report.cgi?x_axis_field=bug_status&ctype=html&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=
Updated URL to return query for all unconfirmed, assigned and new bugs. Bug 1771 - FIXED ? Bug 1797 - Still valid ? Bug 2910 - Still valid ? Bug 3193 - done elsewhere: http://glis.sourceforge.net - WONTFIX? Bug 3523 - FIXED Bug 3296 - WONTFIX Bug 3485 - INVALID ? Bug 3578 - INVALID Bug 3585 - FIXED ? Bug 3778 - Gentoo Statistics? Bug 3882 - FIXED ? Bug 3888 - FIXED ? Bug 3908 - FIXED / WORKSFORME Bug 3943 - Forgotten ? Bug 4006 - FIXED Bug 4023 - FIXED ? Bug 4151 - "I will get review it in the next few days and merge it." ? Bug 4230 - FIXED or a dup of Bug 11275 Bug 4268 - If it's not FIXED, it's a 2s fix and should be done. Bug 4315 - FIXED ? Bug 4595 - FIXED (WORKSFORME and is old) Bug 4634 - FIXED ? Bug 4709 - WORKSFORME
Oh hell, two messed up links there. Bug 3191 (not 3193) Bug 3253 (instead of 3525 - don't ask me how I got to that number)
one more request to join the janitor group, adding cc :)
bug 5078 - fixed in latest stable bug 12382 - fixed in latest bug 14636 - seems fixed bug 21038 - fixed or wontfix? bug 21206 - fixed or wontfix?
bug 30794 - pepkac (user error)
What's the official policy wrt old inactive bugs, or bugs logged against old versions? For instance, there's about a gazillion "NEW" bugs logged against LiveCD 1.4rcX, all of them inactive for months. IMHO this justs makes it more difficult to find current, relative bugs that can be actively fixed. LiveCD related: bug 13120 - fixed bug 13174 - fixed? /wontfix bug 13864 - fixed bug 15184 - fixed? bug 15375 - fixed? bug 16117 - fixed bug 16837 - fixed? bug 17683 - fixed? bug 18904 - fixed bug 19055 - fixed bug 19075 - another inactive bug with almost 0 hope bug 20123 - fixed? bug 21560 bug 21725 - duplicate of bug 21560 bug 22690 - another wontfix bug 23295 - fixed or wontfix? It's an old bug, so pick one other: bug 14053 - old - fixed bug 14551 - old - fixed bug 22942 - fixed
bug 9008 Bug 8495 bug 7155
It seems like nobody really cares about this, so I'm also slowly losing interest. Who knows... this might be my last post. all bugs have been inactive for more than 90 days: bug 13389 - fixed bug 21283 - fixed bug 22627 - fixed bug 18012 - fixed bug 26836 - TEST-REQUEST bug 13225 - TEST-REQUEST bug 13574 - fixed bug 17202 - fixed bug 18166 - TEST-REQUEST bug 20506 - NEEDINFO bug 21291 - fixed bug 21491 - fixed bug 22416 - TEST-REQUEST bug 22749 - fixed bug 26168 - cantfix
I agree - nobody seems to care. My initial point was that really this is for some people, who don't have the time to commit as developers, to help out the developers who don't have the time to clean up the old bugs. 'Post here' just isn't working because the postings aren't being followed up.
bug 17971 - test-request bug 22465 - invalid bug 22989 - fixed bug 8592 - fixed (was never an issue afaik) bug 11071 - fixed or will never be bug 11127 - fixed bug 16332 - fixed bug 17949 - fixed bug 19960 - needinfo bug 22158 - cantfix bug 23668 - fixed
bug 23968 - fixed bug 25105 - fixed bug 25275 - cantfix bug 10996 - fixed
Charles et al, I want you guys to talk to me about this janitor group thing. I don't think I completely understand it. But, I am sorry for not following up on this. If possible, find me on irc and let's talk there.
most of those bugs are now closed ... some remain open because they should be ...
Will Process this one this weekend
I focussed on major,critical and blocker bugs older than 90 days today. Some are not fixed and has very little hope to be reproduced or fixed. Ever. bug 17688 - fixed bug 19701 - WORKSFORME (chances of reproducing are slim to none) bug 19851 - fixed bug 19920 - fixed bug 20244 - possible dup of bug 19851 or user error - fixed bug 20610 - need more info bug 20677 - need more info bug 21369 - fixed bug 21224 - fixed or needinfo bug 21498 - invalid (likely user error) bug 21956 - test-request bug 22039 - CANTFIX ? bug 22546 - wontfix ? bug 22690 - need more info bug 22723 - test-request bug 22846 - a possible portage bug that was fixed? bug 22893 - dup of bug 22039 bug 24159 - invalid bug 24340 - dup of bug 22546
Some severe bugs, currently inactive for more than 90 days: bug 11575 - TEST-REQUEST bug 12521 - TEST-REQUEST bug 14855 - fixed bug 15153 - fixed? bug 19082 - WORKSFORME bug 19088 - fixed (should bugzilla be used in this way to remind us of serious problems in the past?) bug 19729 - fixed ? bug 19861 - WORKSFORME bug 19890 - fixed / LATER bug 20244 - fixed / possible dup of bug 19851- notice the version of fontconfig bug 21675 - TEST-REQUEST bug 21988 - TEST-REQUEST bug 22010 - fixed ? bug 22072 - fixed ? bug 22394 - LATER ( It doesn't look like gamecds are actively develloped anymore) bug 22722 - fixed bug 23390 - TEST-REQUEST bug 26103 - INVALID (really user error. The installation guide says clearly to use i686 for durons) bug 26649 - fixed
please visit http://bugs.gentoo.org/links.html for a temporary link to all bugs older than 90 days and such... more will be added as time goes on and then moved to preset queries. Charles Goodwin and Andrew Cook have both been moved to the bugs-janitor group... An alias has also been created to send both of you email when you use bugs-janitor@gentoo.org mail. All that needs to be done is a better process at labeling this bugs, seemant suggested changing bugs to add a CC, there's currently 750 bugs, I think adding a CC to that list and closing it should suffice, without adding it to a random 750 bugs
looks like Charlie and Andrew are up and running, so closing this bug
