From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C6078138247 for ; Sun, 5 Jan 2014 22:35:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32C41E0B85; Sun, 5 Jan 2014 22:35:10 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 966EEE0B54 for ; Sun, 5 Jan 2014 22:35:09 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id B4BBA33F2A1; Sun, 5 Jan 2014 22:35:08 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Bugzilla workflow Date: Sun, 5 Jan 2014 17:35:11 -0500 User-Agent: KMail/1.13.7 (Linux/3.12.1; KDE/4.6.5; x86_64; ; ) Cc: Sebastian Luther References: <52C9D710.2010308@gmx.de> In-Reply-To: <52C9D710.2010308@gmx.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1971166.2ZsRU3zVog"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201401051735.12581.vapier@gentoo.org> X-Archives-Salt: 29c00cec-d1ab-4e8b-94b9-d3dcaee60e3b X-Archives-Hash: 20689d19591ee5e8f8a6dadeb5afdadb --nextPart1971166.2ZsRU3zVog Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Sunday 05 January 2014 17:05:04 Sebastian Luther wrote: > For now I tried to handle bugs like Zac did. That is: >=20 > There always exists a tracker bug, named: > "[Tracker] sys-apps/portage-". would be nice to start adding an alias field. this way you can do: https://bugs.gentoo.org/show_bug.cgi?id=3Dportage-2.2.8 > 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 i= t? you can add a bug blocking the release tracker that hasn't yet been fixed i= n=20 git. the InVCS tag let's people filter between the two states. > 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? i don't personally care about any of those, but some people find it useful.= =20 they all make sense, so it's just a matter of people using them to keep tra= ck=20 of things. =2Dmike --nextPart1971166.2ZsRU3zVog Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJSyd4gAAoJEEFjO5/oN/WBvmkQAMoUyGl6o1XXMhmS0lLRu5XP J42RY4Iusx9OzGzNz89kb3MrSOnhvjbGBaBaB2JU5iMgUDAGHwopv4/xMBhnhW/L yckPHMsYWqIl9hHciCNQeQHTCm5MjwTwAVun1C5Bq9mFpsUqkIYRrkeOAniTFsGa u56XeGPjh21+kZoepycLeYE7ZVpfGAdqRd5qHm+ysVGC0GUT23THdm1XRckhgLJ+ FpFBTf4XuM8J1nfL7r0oNN27Cljd3JuJvc5+MPu9srC5k4EyN75b/PWd3p9jKNkp xRUUusWmisU0mT/JTh8088F/Y1PIDpjUOfRFjwoN1ACPTeqPmi55iP9x9pj4NQg+ 6Ym7zuZMI6zA7GfqV+QN5V2eXRFmggfVd6kMGTYID0NEs9cgREyAtc5C82fEBaBZ H0AEnoKyIUfsO5XE7RtF+70cOKj4xF1oOBxXH8Fu3ibQ0ZhfafwjvXXfU/yID23j 91dUcSUZw4jJSV5ug36FShKKvWigHaICjLa8Ol48k6dZ7MQm8i/1+14OVovnxSb5 vsiXhr+oVu6/NfHySaAWK+mZxYP63vOOtA7GI7v1trVniawOrIpZ3zkwcd/W5jsE LdJyEjyFtrsJqCCHTRY5oU+3vk+LRY+NBXamxDcaupN7WltSb2a4xxzegElHX2Y8 HUv+6vdGGVDeyK7ubjyC =Z3qx -----END PGP SIGNATURE----- --nextPart1971166.2ZsRU3zVog--