Re: [gentoo-portage-dev] Bugzilla workflow

[Brian Dolbec]

On Sun, 2014-01-05 at 23:19 +0100, Alexander Berntsen wrote:
> On 05/01/14 23:05, Sebastian Luther wrote:
> > I like this workflow because it makes it easy to see what has been
> >  fixed since the last release. The only thing I have no use for, is
> >  this InVCS keyword. I do not know what Zac used it for. Does
> > anyone have a use for it?
> I'm not sure what your confusion is. When a fix is pushed, it is InVCS.
> The bug is not SOLVED, because it only InVCS, not in a release.
>
> > Another topic is the bug status for open bugs, i.e. CONFIRMED,
> > UNCONFIRMED, IN_PROGRESS. I've never bothered with changing them
> > and haven't found them useful, but Brian suggested to use
> > IN_PROGRESS at times. What are your thoughts?
> My interpretation is that CONFIRMED bugs are bugs that a developer is
> able to reproduce, and IN_PROGRESS bugs are bugs that a developer is
> presently working on a fix for.
>
> CONFIRMED is, in my opinion, very useful. IN_PROGRESS is not that
> interesting.

Oh, but it does has uses.

If you open the tracker bug.  The bug numbers listed as blockers.
Hover your mouse over the bug number.  A small popup window appears and
shows the bug summary and status.  The keywords are not listed.  So, for
a bug that has a fix in git for already.  If you change the status to
IN_PROGRESS, then that status is visible in the popup.  Making it easier
to not keep revisiting a bug only to discover it is already fixed.  Same
applies to the bug search page.  The status is shown, but not the
keywords.

I don't know about you, but even though I have a good memory for
numbers.  It is not that good.  They all look alike ;)