1 |
On Sun, 19 Jan 2014 04:10:20 -0500 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> i disagree. dev-portage@ get's cc-ed on bugs when they're being kept |
5 |
> abreast of developments (like PMS), or someone just wants an |
6 |
> opinion/feedback on an issue. so there's no way to differentiate |
7 |
> between bugs that are assigned to the portage team and bugs where the |
8 |
> portage team's opinion is being requested. i want a query for the |
9 |
> former and i just rely on generated bugzilla e-mails for the latter. |
10 |
|
11 |
We have a whole product that tracks the bugs as well as individual |
12 |
components; as a query can be made for that, this forms no problem. |
13 |
|
14 |
Whether Portage is CC-ed is out of this context. |
15 |
|
16 |
> what's wrong with using the whiteboard ? it's a free text field and |
17 |
> you can easily construct a query that produces exactly what you |
18 |
> want. just stick in your username in there. |
19 |
|
20 |
This is a very good idea; I think that I can also search the URL, we |
21 |
could make it commonly known that if the URL or whiteboard respcetively |
22 |
contains a patch or a name that we know the person works on it. |
23 |
|
24 |
> On Tuesday 14 January 2014 21:58:38 Tom Wijsman wrote: |
25 |
> |
26 |
> > InVCS becomes redundant; other than that, good. |
27 |
> |
28 |
> i don't see how it's redundant. there is no other flag that |
29 |
> indicates things have been fixed in the git tree and the only reason |
30 |
> the bug remains open is that a release has not yet been cut. |
31 |
|
32 |
It is redundant because IN_PROGRESS would mean that it is in VCS; which |
33 |
is needed for better overview on the tracker, hence setting InVCS would |
34 |
add no extra meaning but just reflect the IN_PROGRESS status. |
35 |
|
36 |
-- |
37 |
With kind regards, |
38 |
|
39 |
Tom Wijsman (TomWij) |
40 |
Gentoo Developer |
41 |
|
42 |
E-mail address : TomWij@g.o |
43 |
GPG Public Key : 6D34E57D |
44 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |