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 07F001382BD for ; Thu, 16 Jun 2016 13:02:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9C455E0AD6; Thu, 16 Jun 2016 13:02:22 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9D605E0AB0 for ; Thu, 16 Jun 2016 13:02:21 +0000 (UTC) Received: from pomiot (d202-252.icpnet.pl [109.173.202.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id BE27133BE2F; Thu, 16 Jun 2016 13:02:19 +0000 (UTC) Date: Thu, 16 Jun 2016 15:02:13 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Cc: Subject: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Message-ID: <20160616150213.47f09bc4.mgorny@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/oIJitRVGj9J7k1Ig5_CebK+"; protocol="application/pgp-signature" X-Archives-Salt: 5b198754-bcef-4ff5-8553-5ffc7c4da752 X-Archives-Hash: ecae36137bfa350876473c48ec608318 --Sig_/oIJitRVGj9J7k1Ig5_CebK+ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, everyone. Here's the third bugs.g.o redesign RFC. This time it's about closed bugs. Right now we have two states for them: RESOLVED and VERIFIED. RESOLVED is the usual state that the developers use when they close a bug. It's also the only state that could be directly transferred from other states. VERIFIED is used scarcely, and not really consistently. It can only be used on RESOLVED bugs, and sometimes users use it to confirm that the bug is resolved. To be honest, I don't really see the need for VERIFIED state. Since it's used scarcely, it can't be really relied upon. Some users use it completely incorrectly (e.g. when the bug should be reopened instead). What I'd like to introduce instead is a new STABILIZED state. It would -- like VERIFIED now -- be only available for bugs already RESOLVED, and it could be used to signify that the fix has made it into stable. While this wouldn't be really obligatory, it would be meaningful for trackers that need to ensure that fixes in packages have made it to stable -- like the functions.sh use tracker. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/oIJitRVGj9J7k1Ig5_CebK+ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXYqNVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOkjsQAIUGf68zuW94kRCSPWJN7mik GCOwPyi5ZQO4mzQz/P/Mqk8OXofkr47PmbwERYjWm6ANRDHHZiQieuE9Ec7bDUcS qFw/JNnV0KmopkC81awadCW5Dfucm1EVHS6NQYqzP+eE/wOT2WA+7w7cdP2ddwsS tLCUmppHko90HgkqWktX8vEAAnYuqzqqT+CiqG+y3F8SqsnBb4HLjiq9twuw8QA+ KbMU5WF3PwgehQ46utnNtGyEz74Y5WsxNujJ2yHL5msyNZmBvnhN228fk9ApRYAe 0tuDKXDN6vsgJRU4nB6qAljiBElQa6tkI5MA93KaLHsU2LpZxZFl+aQn+jSL5WKu BoJNNUZLHBUq01ubw2LJnjKHcjR+kfcmwiwAVarjTqsbvopBMYH+HueHX75vSX8p DLDsDz3TXgQl46FAJRPCjU99m7C/XM0q7kKVah25KP5uAnZ9nV/WsUOD8UaIbV6f yNZWSq/JSZUWALEgwdSskn+aPiLQx6O3N/bW3CIPrfLDFT9EmzmjmQdts+C1C6+o 34xOYJ2II38kfzr7OLIpBcQ8JmYUIaOS7nt/2he9TY3aiczdUVB7mDim8cYq6sdk WuoTDFZBxj2znSnpa4OiaACUs8lO6EXh8oCb+2DHNIU2LQKJtkOrZy74OCWElI8I dNkp95KU8Y2w5yBIsyN+ =TdgQ -----END PGP SIGNATURE----- --Sig_/oIJitRVGj9J7k1Ig5_CebK+--