1 |
21.06.2013 23:08, Andreas K. Huettel пишет: |
2 |
> Am Freitag, 21. Juni 2013, 14:50:29 schrieb Markos Chandras: |
3 |
>> On 21 June 2013 12:44, Tomáš Chvátal <tomas.chvatal@×××××.com> wrote: |
4 |
>>> 2013/6/21 Pacho Ramos <pacho@g.o> |
5 |
>>> |
6 |
>>>> Could "maintainer-wanted" assigned bugs be filtered? Otherwise we see a |
7 |
>>>> ton of that kind of bugs that, I think, we already know can become |
8 |
>>>> really old ;) |
9 |
>>>> |
10 |
>>>> Thanks! |
11 |
>>> |
12 |
>>> You can do such yourself. Just clone the repo [1] and commit the updated |
13 |
>>> links. |
14 |
>>> |
15 |
>>> Also my plan was to list even m-w bugs, because even those suckers get |
16 |
>>> obsoleted often so we should close them. |
17 |
>>> |
18 |
>>> Cheers |
19 |
>>> |
20 |
>>> Tom |
21 |
>>> |
22 |
>>> [1] |
23 |
>>> http://git.overlays.gentoo.org/gitweb/?p=proj/qa-scripts.git;a=summary |
24 |
>> |
25 |
>> That is true. There is nothing special about there m-w bugs. They are |
26 |
>> still unresolved bugs, for many years. No need to treat |
27 |
>> them differently. |
28 |
>> |
29 |
> |
30 |
> How can a m-w bug be resolved? Adding the package is unlikely to happen if |
31 |
> last request came years ago. |
32 |
> |
33 |
> My suggestion would be (this is how I handled it in printing): |
34 |
> |
35 |
> 1) leave message on bug |
36 |
> "Is anyone still interested in this?" |
37 |
> |
38 |
> 2) if noone replies in 2 months, resolve as obsolete |
39 |
> |
40 |
> |
41 |
IMO maintainer-wanted@ bugs can be resolved only in two ways: |
42 |
|
43 |
1) package accepted into main tree, bug is closed as FIXED. If package |
44 |
sits in sunrise - it's not a solution and bug should not be closed; |
45 |
2) package has dead upstream, does not build with current |
46 |
gcc/glibc/binutils/whatever and can not be fixed - bug is closed as |
47 |
OBSOLETE. |
48 |
|
49 |
-- |
50 |
Best regards, Sergey Popov |
51 |
Gentoo developer |
52 |
Gentoo Desktop-effects project lead |
53 |
Gentoo Qt project lead |