1 |
mmm.... yes java@g.o would be a good place instead of here to email |
2 |
it. |
3 |
|
4 |
Basically the aim I have for this is too draw the attention of you dev's to |
5 |
bugs that are a 'quick' fix. |
6 |
|
7 |
Therefore meeting the aim of closing bugs without you guys having to do most |
8 |
of the investigation... |
9 |
|
10 |
I have also though of going thru bugs.gentoo.org and reassigning the |
11 |
priority of bugs into categories (rather a large job for anyone who has |
12 |
other projects they want to get kicking). |
13 |
|
14 |
eg (as a very ruff guess) |
15 |
So P1 would be for security exploits and the like. |
16 |
P2 would be for ebuild related buys |
17 |
P3 ebuild request |
18 |
P4 ebuild request that are extremely difficult (or just can't happen because |
19 |
of lack of resources) |
20 |
P5 (something even worse than above) |
21 |
|
22 |
I also believe that there should be some bugs marked as WONTFIX, CANTFIX. |
23 |
|
24 |
For example jboss https://bugs.gentoo.org/show_bug.cgi?id=148383 and |
25 |
https://bugs.gentoo.org/show_bug.cgi?id=66965 |
26 |
|
27 |
I believe, and it will be interesting in hereing your views on this, that |
28 |
bugs should only be open if they are actually going to be worked on. With |
29 |
jboss we now have a binary ebuild in the overlay that could replace the |
30 |
existing versions and these jboss bugs could be closed. |
31 |
|
32 |
What do you guys think? |
33 |
|
34 |
Alistair (ali_bush) |
35 |
|
36 |
|
37 |
On 1/17/07, William L. Thomson Jr. <wltjr@g.o> wrote: |
38 |
> |
39 |
> On Wed, 2007-01-17 at 11:53 +1300, Alistair Bush wrote: |
40 |
> > How about I start opening bugs on bugs that have already been fixed |
41 |
> > but not closed :) |
42 |
> |
43 |
> Hmm not sure about that. Buggzie seems stable these days, but still |
44 |
> might be excessive use. Would like to know what others think about that. |
45 |
> |
46 |
> > something like |
47 |
> > |
48 |
> > Bug #123456 is open even tho its been fixed. |
49 |
> > |
50 |
> > I wonder what the bug-wranglers would like of that :D |
51 |
> |
52 |
> Well another route would be to email bug #, and comments to |
53 |
> java@g.o Then the first dev that gets the email can take comments |
54 |
> add to bug and close the one. Instead of having to close and comment on |
55 |
> two :) |
56 |
> |
57 |
> To expand that, you could email over a list of bug #s with comments, to |
58 |
> kill more than one bird with a single stone. ;) |
59 |
> |
60 |
> -- |
61 |
> William L. Thomson Jr. |
62 |
> Gentoo/Java |
63 |
> |
64 |
> |
65 |
> |