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 A17241382BD for ; Fri, 17 Jun 2016 09:03:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4C5EB94086; Fri, 17 Jun 2016 09:03:37 +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 6B4E6E0C29 for ; Fri, 17 Jun 2016 09:03:36 +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 F1E3933FEDE; Fri, 17 Jun 2016 09:03:33 +0000 (UTC) Date: Fri, 17 Jun 2016 11:02:45 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Cc: Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Message-ID: <20160617110245.49823b35.mgorny@gentoo.org> In-Reply-To: <20160616150213.47f09bc4.mgorny@gentoo.org> References: <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_/5/UrP4nS2wQr9PXQLiHIUoS"; protocol="application/pgp-signature" X-Archives-Salt: 68029eaf-1f65-472e-b046-5673959e74cb X-Archives-Hash: eca7390e0cb4ea7a2312a79f6d7e3a92 --Sig_/5/UrP4nS2wQr9PXQLiHIUoS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 16 Jun 2016 15:02:13 +0200 Micha=C5=82 G=C3=B3rny wrote: > Hello, everyone. >=20 > Here's the third bugs.g.o redesign RFC. >=20 > This time it's about closed bugs. Right now we have two states for > them: RESOLVED and VERIFIED. >=20 > 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. >=20 > 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. >=20 > 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). Since nobody seemed to mind, I've disabled VERIFIED now. I've also loosened the workflow so that all (old) VERIFIED bugs can be reopened directly. For stabilization thing, I'm going to wait for more replies/ideas. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/5/UrP4nS2wQr9PXQLiHIUoS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXY7y2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOC7kP/RkKRpRm4ouiCoTywuYTiuaa fyAL1ufkDz/9akPJu0yD9xy+ne7oV6BtMuSGa/hNe6RaeIzoYemiCt5bjAwmQSt8 +rLzzmQyqMe/Tg2Pd2AJQBfcXTT6avuratT1Xhtt+vDZAlaEO4k6VluUcsjMLm9K tRNBqkRCZVeGNE8seHi315w625rHNuRjie4ScLpDbp5dhP/9pcCJG7s8+kEtMpYd MWUrHj+j2y/WtlRAJFI/PcEJRJ6ksBBGj3tjLy9xMkW2+jmC6wuZy/42qKH7JD58 oeEsujEFFCF6IgZkrI+Ap00svmGeGPbGoy+QS/kCvK96dvOBrhSnP2vc/9UmIAno eO+GkYQqjrjteeCnU8Vzc7TcTaseUT/KafGnqHkhlqEjuHtX768UHB+uEO8PVreo u9H58IGBIm/41YDrWU5vkdPgciwyqYqW1NXeJheE8jDvJKMLawaOxG7/hxjqNnvM yKAXyjKDxy+wp4jGp4pDc9i5BwvRXHOTnp6prM27JGtbdS5+a+iywFAHG+GCe64l wiMYF4OarkYlMwIhM0AQM5fMnv3/YeaHO2AcENIOps7oNdTBb4j1i7e7TpK3Ey5Y V4/H0OvQ7LAeE+UP9yPS4VSYCbO+m54TFpOUzFUDBIehi6dpIKojziikBazrG39u VtZ8Q19akMD6ydaZdT2l =2XWt -----END PGP SIGNATURE----- --Sig_/5/UrP4nS2wQr9PXQLiHIUoS--