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 23A7D1382BD for ; Thu, 16 Jun 2016 13:19:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5EBACE0B37; Thu, 16 Jun 2016 13:19:25 +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 588CBE0B33 for ; Thu, 16 Jun 2016 13:19:24 +0000 (UTC) Received: from red.yakaraplc.local (host213-123-185-55.in-addr.btopenworld.com [213.123.185.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: chewi) by smtp.gentoo.org (Postfix) with ESMTPSA id 257563406F2 for ; Thu, 16 Jun 2016 13:19:22 +0000 (UTC) Date: Thu, 16 Jun 2016 14:19:16 +0100 From: James Le Cuirot To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Message-ID: <20160616141916.574f14d0@red.yakaraplc.local> In-Reply-To: <97fb2871-962e-4efa-5c75-6a57ba12eaba@gentoo.org> References: <20160616150213.47f09bc4.mgorny@gentoo.org> <97fb2871-962e-4efa-5c75-6a57ba12eaba@gentoo.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-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: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 28f7d777-c956-488d-9aa2-d1ba8aa748e4 X-Archives-Hash: 3e172bc5b025752b88b72f02fde2d735 On Thu, 16 Jun 2016 15:14:44 +0200 Kristian Fiskerstrand wrote: > > 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. > > The description of InVCS keyword in bugzilla is: > InVCS Fix has been added to a VCS(either CVS, SVN, Git, ...) > repository. Will be closed when fixes are applied to a stable level > package. > > A bug isn't resolved until it is fixed in a stable package (for > packages ever in stable to begin with), but InVCS keyword can be used > by developers to filter out the bugs for issues to work with. I > oppose a change to that behavior, although I would like to see it > being used more consistently as it seems quite a few developers are > neglecting the stable tree. I currently set InVCS for pending-stable fixes in conjunction with the IN_PROGRESS state. I would like to keep InVCS at least. -- James Le Cuirot (chewi) Gentoo Linux Developer