21.06.2013 23:08, Andreas K. Huettel пишет: > Am Freitag, 21. Juni 2013, 14:50:29 schrieb Markos Chandras: >> On 21 June 2013 12:44, Tomáš Chvátal <tomas.chva...@gmail.com> wrote: >>> 2013/6/21 Pacho Ramos <pa...@gentoo.org> >>> >>>> Could "maintainer-wanted" assigned bugs be filtered? Otherwise we see a >>>> ton of that kind of bugs that, I think, we already know can become >>>> really old ;) >>>> >>>> Thanks! >>> >>> You can do such yourself. Just clone the repo [1] and commit the updated >>> links. >>> >>> Also my plan was to list even m-w bugs, because even those suckers get >>> obsoleted often so we should close them. >>> >>> Cheers >>> >>> Tom >>> >>> [1] >>> http://git.overlays.gentoo.org/gitweb/?p=proj/qa-scripts.git;a=summary >> >> That is true. There is nothing special about there m-w bugs. They are >> still unresolved bugs, for many years. No need to treat >> them differently. >> > > How can a m-w bug be resolved? Adding the package is unlikely to happen if > last request came years ago. > > My suggestion would be (this is how I handled it in printing): > > 1) leave message on bug > "Is anyone still interested in this?" > > 2) if noone replies in 2 months, resolve as obsolete > > IMO maintainer-wanted@ bugs can be resolved only in two ways:
1) package accepted into main tree, bug is closed as FIXED. If package sits in sunrise - it's not a solution and bug should not be closed; 2) package has dead upstream, does not build with current gcc/glibc/binutils/whatever and can not be fixed - bug is closed as OBSOLETE. -- Best regards, Sergey Popov Gentoo developer Gentoo Desktop-effects project lead Gentoo Qt project lead
signature.asc
Description: OpenPGP digital signature
