Gentoo Archives: gentoo-portage-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-portage-dev@l.g.o
Cc: Sebastian Luther <SebastianLuther@×××.de>
Subject: Re: [gentoo-portage-dev] Bugzilla workflow
Date: Sun, 05 Jan 2014 22:35:10
Message-Id: 201401051735.12581.vapier@gentoo.org
In Reply to: [gentoo-portage-dev] Bugzilla workflow by Sebastian Luther
1 On Sunday 05 January 2014 17:05:04 Sebastian Luther wrote:
2 > For now I tried to handle bugs like Zac did. That is:
3 >
4 > There always exists a tracker bug, named:
5 > "[Tracker] sys-apps/portage-<next version>".
6
7 would be nice to start adding an alias field. this way you can do:
8 https://bugs.gentoo.org/show_bug.cgi?id=portage-2.2.8
9
10 > I like this workflow because it makes it easy to see what has been fixed
11 > since the last release. The only thing I have no use for, is this InVCS
12 > keyword. I do not know what Zac used it for. Does anyone have a use for it?
13
14 you can add a bug blocking the release tracker that hasn't yet been fixed in
15 git. the InVCS tag let's people filter between the two states.
16
17 > Another topic is the bug status for open bugs, i.e. CONFIRMED,
18 > UNCONFIRMED, IN_PROGRESS. I've never bothered with changing them and
19 > haven't found them useful, but Brian suggested to use IN_PROGRESS at
20 > times. What are your thoughts?
21
22 i don't personally care about any of those, but some people find it useful.
23 they all make sense, so it's just a matter of people using them to keep track
24 of things.
25 -mike

Attachments

File name MIME type
signature.asc application/pgp-signature