1 |
El sáb, 14-04-2012 a las 12:42 -0300, Alexis Ballier escribió: |
2 |
> On Sat, 14 Apr 2012 13:02:27 +0200 |
3 |
> Pacho Ramos <pacho@g.o> wrote: |
4 |
> |
5 |
> > Hello |
6 |
> > |
7 |
> > From time to time I see old bug reports that are still wrongly opened |
8 |
> > and referring to old packages no longer in the tree. Would be possible |
9 |
> > to add a way to periodically check for bugs referring in summary to |
10 |
> > obsolete packages and, then, allow us to have a cleaner bug list? |
11 |
> |
12 |
> -1, you really cant automate this. |
13 |
> |
14 |
> - for eg, keyword req, the version doesnt really matter and is usually |
15 |
> just there to help but should really be read as latest version; |
16 |
> closing/ignoring the bug while the latest version still lacks the |
17 |
> keywords is just wrong. |
18 |
> - for stablereq, that's a different story |
19 |
> |
20 |
> - for other bugs, some may have been fixed independently upstream, but |
21 |
> usually, they dont fix by themselves, so if a bug didnt get |
22 |
> attention, chances are its still valid. |
23 |
> |
24 |
> |
25 |
> moreover, doing this, you'll just encourage people not to fill the |
26 |
> version |
27 |
> |
28 |
> |
29 |
> IOW: If you want a cleaner bug list, ignore stable/kw reqs, then pay |
30 |
> attention to your bugs and fix them :) |
31 |
> |
32 |
> A. |
33 |
> |
34 |
> |
35 |
|
36 |
It's not for versions, only package names (there are still bugs |
37 |
referring to already removed packages for months) |