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 29FC91382BD for ; Fri, 17 Jun 2016 14:02:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C57D8E0B0A; Fri, 17 Jun 2016 14:02:44 +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 8E128E0AED for ; Fri, 17 Jun 2016 14:02:43 +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 40EC333BF44; Fri, 17 Jun 2016 14:02:41 +0000 (UTC) Date: Fri, 17 Jun 2016 16:02:34 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Rich Freeman Cc: gentoo-dev , Kristian Fiskerstrand , bugzilla@gentoo.org Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Message-ID: <20160617160234.458de4b2.mgorny@gentoo.org> In-Reply-To: References: <20160616150213.47f09bc4.mgorny@gentoo.org> <97fb2871-962e-4efa-5c75-6a57ba12eaba@gentoo.org> <20160617155250.5d89cd7d.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_/qMsowWBmwinsSVORGJuf5hz"; protocol="application/pgp-signature" X-Archives-Salt: bfc42706-4b63-4c71-a26b-2ef847e28d16 X-Archives-Hash: e463a76a66ed43c4e74e798c3e3feaf9 --Sig_/qMsowWBmwinsSVORGJuf5hz Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 17 Jun 2016 09:58:52 -0400 Rich Freeman wrote: > On Fri, Jun 17, 2016 at 9:52 AM, Micha=C5=82 G=C3=B3rny wrote: > > On Thu, 16 Jun 2016 15:14:44 +0200 > > Kristian Fiskerstrand wrote: > > =20 > >> On 06/16/2016 03:02 PM, Micha=C5=82 G=C3=B3rny wrote: =20 > >> > Hello, everyone. > >> > =20 > >> > >> > >> =20 > >> > > >> > What I'd like to introduce instead is a new STABILIZED state. It wou= ld > >> > -- 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 > >> > >> 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 pa= ckage. > >> > >> A bug isn't resolved until it is fixed in a stable package (for packag= es > >> 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 mo= re > >> consistently as it seems quite a few developers are neglecting the > >> stable tree. =20 > > > > How would that work for Portage? There 'InVCS' indicates that the fix > > has landed in git (i.e. in -9999, not yet released). > > =20 >=20 > That could actually be generalized. I could see many types of bugs > where the issue is with upstream, and we might want to track the > progress as upstream implements a fix, releases it, and then it is > stabilized on Gentoo. So, maybe we need another state to track in > upstream's VCS vs the Gentoo repo. >=20 > Another approach would be to distinguish between portage as a > Gentoo-hosted upstream, and portage as a package in the Gentoo repo. > The same could apply to any Gentoo-hosted project. We also have the 'STABLE' keyword. However, we're getting to the point where bug lists are already twice as wide as my monitor (since I had to include keywords...). --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/qMsowWBmwinsSVORGJuf5hz Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXZAL7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOBJMQAOJrl3RsvHjmrWexARQITUL2 jQZWE2D7ga5NnYWoQzx30QR29JU+2pViMj3/w0DQSIsJPkcVE2kNJezu94KRrrud rQCdUA7C3oTXCGPKVwyXD0XtyRxF5ZOfTFukvpDvGpvMyP/sbZ6Pwg5m507NHbS1 A4L+MQTLyHCZMoJRJ86Vctu29hM5AJ0fxWT05vMyF4/JCTvMoSiywRfc1ZJIGbXm zrQwBSK4PkBrEi0EFYYHYCzRTxuI5+NarA8K9mIrk4osxXxHyJW6WqqnRelGi3CP FbRe1UiefWrapEMTRKYN5xP7WWILZ0uVUrRCDeG7DNWh7AgapcHWdy3rStjtHMFY ioLx43ISpnyksTuGJtiAEFL4w8aRAEcQRMyXUkyQh+dUW1ifXlN1C3oYtXT0zxWr HI/UeRKBGrFCb/u5PfpULayvhhCzGHOzm6HcmXjDUM8YB0XfsQSHYNPa85Umtfnl HNekGlPNqq867gRpcZLUuVNxwzCw/J6cvV2KEpM0GMyzH/SqlyMkZgySs4ZqBkwe +0wMvOn5Af4b2XDNGxX/phCm3NR9tiDP/Qe37peMoUIeY4ujrH24E67QAUDzJOby 085sYpbtPDJ+9nD+RLUKfUhaxeXlfPcKKGTnOgV5OzZF8tb/dgHYKCCcWoDhLfZw yasqVRnoTJrdZTmgqkZi =0n7T -----END PGP SIGNATURE----- --Sig_/qMsowWBmwinsSVORGJuf5hz--