Re: [gentoo-portage-dev] Bugzilla workflow

[Tom Wijsman <TomWij@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

On Sun, 19 Jan 2014 04:10:20 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> i disagree.  dev-portage@ get's cc-ed on bugs when they're being kept
> abreast of developments (like PMS), or someone just wants an
> opinion/feedback on an issue.  so there's no way to differentiate
> between bugs that are assigned to the portage team and bugs where the
> portage team's opinion is being requested. i want a query for the
> former and i just rely on generated bugzilla e-mails for the latter.

We have a whole product that tracks the bugs as well as individual
components; as a query can be made for that, this forms no problem.

Whether Portage is CC-ed is out of this context.

> what's wrong with using the whiteboard ?  it's a free text field and
> you can easily construct a query that produces exactly what you
> want.  just stick in your username in there.

This is a very good idea; I think that I can also search the URL, we
could make it commonly known that if the URL or whiteboard respcetively
contains a patch or a name that we know the person works on it.

> On Tuesday 14 January 2014 21:58:38 Tom Wijsman wrote:
>
> > InVCS becomes redundant; other than that, good.  
>
> i don't see how it's redundant.  there is no other flag that
> indicates things have been fixed in the git tree and the only reason
> the bug remains open is that a release has not yet been cut.

It is redundant because IN_PROGRESS would mean that it is in VCS; which
is needed for better overview on the tracker, hence setting InVCS would
add no extra meaning but just reflect the IN_PROGRESS status.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]