From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A42FE13832E for ; Mon, 15 Aug 2016 04:05:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2B7B9E0BEF; Mon, 15 Aug 2016 04:05:49 +0000 (UTC) Received: from mail-pf0-f195.google.com (mail-pf0-f195.google.com [209.85.192.195]) (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 24986E0B2A for ; Mon, 15 Aug 2016 04:05:47 +0000 (UTC) Received: by mail-pf0-f195.google.com with SMTP id i6so3075279pfe.0 for ; Sun, 14 Aug 2016 21:05:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=perfinion-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ORE5DsWpnEIFRx95Ydy4KE9oVcZFXxnugojn6lN1pwc=; b=bMRvzlUshuuu2VOhP8p5EEac4XfTXnoSGNsPX9fpitm/KtYapjvzD4sQkbb2Zxj2iF qnrGGlgDbapJg6a+vX59Mvl2nKmF51WMxwtr0COMOapTcZMY2ZjpQKWyiDe61I7o7FA8 wvefsOcwdwge6v7MTZumXAqCp/hVAV1w556ub0fhJ6qrnvNC9bNYR6h2foXQXtWpf3Xa fBmWGCjjyQD60PF+apVxozg2RSe9vHKHQLjItw0dleSexGugOAwR4YA/G4kQXv2GM26A 1c3K3eHU7M6osA119vctgcpBO7sGcPB8d9ou0lQp/UqCBbiIdQnIXX4+wwIeFEl9vhVk Ukqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ORE5DsWpnEIFRx95Ydy4KE9oVcZFXxnugojn6lN1pwc=; b=DpUa2cQX53xpVbQA6j83MHDSsq9tXBVdd/4g4xCZqDuhLriq2gUBgXzP/xk3d2cKXV /yujJqQNPdmp7v8VPB9Q/R+uZ/Od/+WdCRGw0d6OSLzqHB1ULDiewkRale4xfubECht2 xGSj3p1Kkm/Rm0R90/i9kZPDthb3jL/OqsF0xTqlCDC38V7BYpAynpyhHeeUkaXv0HmF R6tIvVDb69slCVa717F7p2fVTgx6kpTg7YCrlL8oOxCS6VTLdo5x/UwkP27fhGHUybZU QIZsnZ42KPQ4xizJ7VoIPuqD6tKdaiSccbpOpADI8SEXb2Q5ktaVdE/vK8hE2OVOm0Ik yduw== X-Gm-Message-State: AEkoousirMQxX2vuOUy7Qm5WnTQH5ICCo0FJNuS2F0t/kn1bsckC9mcjwERBFYffx/rQ8Q== X-Received: by 10.98.13.84 with SMTP id v81mr50688908pfi.108.1471233946611; Sun, 14 Aug 2016 21:05:46 -0700 (PDT) Received: from localhost ([2404:e800:e600:57b:18c4:7635:e736:50a1]) by smtp.gmail.com with ESMTPSA id i62sm28858095pfg.62.2016.08.14.21.05.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 Aug 2016 21:05:45 -0700 (PDT) Date: Mon, 15 Aug 2016 12:05:43 +0800 From: Jason Zaman To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New Working Group established to evaluate the stable tree Message-ID: <20160815040543.GA32659@meriadoc.perfinion.com> References: <6046d13b-1a54-aa5e-ab16-df448b0f8c59@gentoo.org> <20160815034522.GB22106@meriadoc.perfinion.com> <20160815155326.41c9c33d@katipo2.lan> 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-Disposition: inline In-Reply-To: <20160815155326.41c9c33d@katipo2.lan> User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: 2d6b5696-69c8-4311-849f-6d752debbf0e X-Archives-Hash: de138d419014df27ed2f1c4a924b26d0 On Mon, Aug 15, 2016 at 03:53:26PM +1200, Kent Fredric wrote: > On Mon, 15 Aug 2016 11:45:22 +0800 > Jason Zaman wrote: > > > IN_PROGRESS == we've put the fix in the git repo > > RESO/TESTREQ == new release and in ~arch > > TESTREQ was incidentally my first thought. Only needs me to study how much that's already used > and whether or not existing bugs with that flag meet that description or not. > > > However, a distinction between IN_PROGRESS and RESO/TESTREQ is not possible here, > because "in git" means "You'll get it if you sync >1h from now" Oh, I meant this is for our policy stuff. which is in hardened-refpolicy.git and then every few weeks we make a release and bump all the packages in sec-policy/selinux-*. For things that do not need an actual release we just skip INPROG and go straight to TESTREQ when we fix the ebuild in the tree. The important part to me is that RESO/FIXED should only mean fixed when the problem is fixed in the stable tree too. There has to be another state before FIXED that is for ~arch. If the package is not stable on any arch then of course it is FIXED as soon as ~arch is fixed. > IN_PROGRESS can thus only mean something about it being worked on but not yet pushed > to the main git repo. (ie: overlays, private repos) > > But I would rather it part of the primary resolution path, not a mere property of the resolution type. > > Because its easier to say: > > UNCONFIRMED -> CONFIRMED -> INPROGRESS -> INVCS -> STABLE > > Than > > UNCONFIRMED -> CONFIRMED -> INPROGRESS -> (RESOLVED/TESTREQ) -> (RESOLVED/FIXED) They are roughly equivalent, yeah. But I prefer TESTREQ because its easier to see in the bug list page. You can of course choose which items are shown in the list in bugzilla but resolution is already there so no need to add an extra column. -- Jason