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 48D33139694 for ; Thu, 30 Mar 2017 17:58:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6F39221C1EA; Thu, 30 Mar 2017 17:58:22 +0000 (UTC) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 3D47321C054 for ; Thu, 30 Mar 2017 17:58:22 +0000 (UTC) Received: by mail-io0-x241.google.com with SMTP id f103so3648823ioi.2 for ; Thu, 30 Mar 2017 10:58:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=tocOb4RGw2LA5+DF5KFzh6n23ORx46KpKI5+MT9uk/k=; b=QTdsXd08W86bQ9Qg+i8poBZetbJzZtxlyZrEoinQuXsbYdTGC3SBkMJOb0j7Qdcv0b k6CDR86aZSjppBO63TDcxfNT5+2skPyMjQsBiBdIrKI/khqf/8KbGrvbRBgmawAKgbcV 5NpOGjyMip8gSoTtveLI/ODFylvyyqCeeSHutTf/J6TSnxj9lnbCspkymwYOswsmju6k 5L8r410H2lbaj6Uh6f/1CrXXX2P0Wsyk4lnczogaIq/HRckEi5GJkpPkE2+YaUqEl0VO armvZ5tPEapTDuaw6N9E06qaK3Q+26Fq8N64WO/HPbLiUwaToFBdR8dqyr7NobantwMM ndhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=tocOb4RGw2LA5+DF5KFzh6n23ORx46KpKI5+MT9uk/k=; b=Qu70NKLJY3o2eOgS2DZZvXjDgOfbpGcdEAdVkCBQCHdKYXTop7DIZlCYtkoX9M2lg8 xHvJFNZvQNS2qLO130og/H0fUZO0u5cPisL1CAUsl0FDvpmU52glI/qVXX1eUb0VOuTz Z7sMe2obDWJb+/yNyUhnCgZqaw6xDhZBTIy50lp8dnu8f+F5rRzhzB+J0TFuCnl46t3R 6UJMqD13U13V8m42+NPH8jDzpQRLjpxrBWr+bWK8MbUvEPLB35a5ZxDzsYv43belnOHm j8DFBgUM5Vp2jfb040+pGyiJWzD40N1KCv/xsI5/2HvxUGxN48XkzGqpkiG5L+buGWIP 6XAg== X-Gm-Message-State: AFeK/H3i0dVUtIk4QNqNKl67WBfTYYol3cDYarqZ6AGrGMy59CIk2qKC97oA1oTerWIw+g== X-Received: by 10.107.149.7 with SMTP id x7mr1892560iod.167.1490896701686; Thu, 30 Mar 2017 10:58:21 -0700 (PDT) Received: from whubbs1.gaikai.biz ([100.42.103.5]) by smtp.gmail.com with ESMTPSA id e195sm5385506itb.18.2017.03.30.10.58.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 10:58:20 -0700 (PDT) Sender: William Hubbs Received: (nullmailer pid 5029 invoked by uid 1000); Thu, 30 Mar 2017 17:58:20 -0000 Date: Thu, 30 Mar 2017 12:58:20 -0500 From: William Hubbs To: gentoo-project@lists.gentoo.org Cc: bugzilla@gentoo.org Subject: Re: [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie Message-ID: <20170330175820.GB4981@whubbs1.gaikai.biz> Mail-Followup-To: gentoo-project@lists.gentoo.org, bugzilla@gentoo.org References: <1490774199.1744.1.camel@gentoo.org> <22747.48686.688050.322661@a1i15.kph.uni-mainz.de> <1490796901.1141.1.camel@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline In-Reply-To: <1490796901.1141.1.camel@gentoo.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: 9765e500-b4bb-4c5b-b95a-2b858398cb9c X-Archives-Hash: 269379b88d778c44c7d4da8cb4db1d2d --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 29, 2017 at 04:15:01PM +0200, Micha=C5=82 G=C3=B3rny wrote: > On =C5=9Bro, 2017-03-29 at 16:01 +0200, Ulrich Mueller wrote: > > > > > > > On Wed, 29 Mar 2017, Micha=C5=82 G=C3=B3rny wrote: > > > I'd like to bring the problem of ambiguity of 'UPSTREAM' resolution > > > on our Bugzilla to the discussion. > > > While the resolution generically indicates an issue upstream, it is > > > used differently by different developers, and sometimes even in a > > > few meanings by a single developer. What's even worse, it is both > > > used as a positive, neutral and negative resolution which renders it > > > kinda meaningless as a classification criteria. > > > [...] > > > How would you feel about removing/disabling the UPSTREAM resolution, > > > and expecting developers to use UPSTREAM keyword + regular > > > resolution? > > > Any other ideas? > >=20 > > Use it in the sense as it is defined in Bugzilla? > >=20 > > UPSTREAM > > The requested bug is considered to be out of the purview of the > > distro and should be submitted/discussed directly with the > > respective upstream project. This could include a number of things > > such as changing default configuration options or behavior, adding > > new options or functionality, or deleting support for older > > systems. > >=20 > > IMHO it would be out of proportion to remove the field, just because > > some developers don't use it as intended. >=20 > What is your plan on making the developers use it correctly? I'm with ulm on this, we shouldn't remove the resolution just because developers haven't been using it correctly; that would be trying to solve a social issue with a technical fix which would make future resolutions invalid. As I said in my other post, resolved/invalid =3D "this is not a bug.", but resolved/upstream =3D "this is out of our scope as a distro, please discussit with upstream." They are slightly different meanings, but I think we should keep both of them. William --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCWN1HOwAKCRBuVBb0MMRl OMcWAJ435Jlv+9RK4fkQ6UicdbuFwe0gGQCeP7jM+PZvR2KamC79BZf+aGM7zJw= =FeaO -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw--