From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Basic questions about the triage process Date: Mon, 28 Dec 2015 12:24:55 -0800 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1451334319 32099 80.91.229.3 (28 Dec 2015 20:25:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2015 20:25:19 +0000 (UTC) Cc: "emacs-devel@gnu.org" To: Andrew Hyatt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 28 21:25:11 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aDeLt-00071T-Gk for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 21:25:09 +0100 Original-Received: from localhost ([::1]:46123 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDeLs-0007kH-BG for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 15:25:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDeLo-0007k8-SX for emacs-devel@gnu.org; Mon, 28 Dec 2015 15:25:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDeLl-0002Mv-LU for emacs-devel@gnu.org; Mon, 28 Dec 2015 15:25:04 -0500 Original-Received: from mail-pa0-x233.google.com ([2607:f8b0:400e:c03::233]:33790) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDeLl-0002MH-FP for emacs-devel@gnu.org; Mon, 28 Dec 2015 15:25:01 -0500 Original-Received: by mail-pa0-x233.google.com with SMTP id cy9so114223553pac.0 for ; Mon, 28 Dec 2015 12:25:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mail-followup-to:mime-version:content-type; bh=VO/IyBbv1PXCfZVayzePmiwGpxbTa5cqazEDXvK3Ezs=; b=bPgSaEt8g6QmWNd6l4Nr00c25lxBZiGKnUev3Mt2OJeDfWN58/otMpQSHPJCg6iyrd jHHxMViXX+HXXxPgvu6FXVDQwzmOb0X0AFkx7raC1fNjenl7zahmoRdIsRQWufxiRWmO lss9f6pb4jFtta75Tg+g0R4f8Uwik7Xq2NgQ+peHj0nJ7eqWXB6ejA/eWfTIwooC7ABn 0yL+TlRex/72+lEcTZUZDlVCmbVvN678HrsnaQ4ZL38jgpfNgaYORQ9PClYRhKOlW9mg AQczPfC6IdDPq8arYkU6LvBHcVLdARgmsX6pQg99S82Cg345UKg1kj4XHitbWAScnX8m zpXw== X-Received: by 10.67.4.100 with SMTP id cd4mr8454590pad.59.1451334300879; Mon, 28 Dec 2015 12:25:00 -0800 (PST) Original-Received: from Vulcan.local (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id dz6sm83293932pab.19.2015.12.28.12.24.59 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 28 Dec 2015 12:25:00 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.local (Postfix, from userid 501) id 1A9F811B731C0; Mon, 28 Dec 2015 12:24:59 -0800 (PST) In-Reply-To: (Andrew Hyatt's message of "Mon, 28 Dec 2015 05:39:04 +0000") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.5 (darwin) Mail-Followup-To: Andrew Hyatt , "emacs-devel\@gnu.org" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400e:c03::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197036 Archived-At: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable >>>>> Andrew Hyatt writes: > 1) How to identify the bugs to be triaged. I actually don't know the set = of > bugs you are interested in. All the open ones? Just the ones blocking ema= cs > 25? If I'm using the debbugs package, what's the command I use to display > just the set we're interested in? There are really two sets of bugs we'd like to pay attention to: 1. Those blocking the release of Emacs 25. Clearly, we can't release until this reaches zero. 2. All the open bugs, especially the oldest ones. If they don't reproduce against emacs-25 anymore, we'd like to mark them closed as fixed in th= at release. #1 is a fairly small list, so just getting more information on those bugs so that the developers know how to proceed next is what's important. #2 is a large list, but would help out the Emacs project by clearing out things we don't need to pay attention to anymore. > Also, what if it does reproduce? I guess just a reply saying that it > reproduces? Or does it need to be tagged in some way? A comment would be valuable, and if what you saw still matches the descript= ion of the problem. > Sorry, maybe there was a document that explains this all, and I missed it. > If there's isn't such a document, I think it'd be pretty helpful. Perhaps we do need a targeted document for on-boarding bug herders. If, whi= le you're learning this process, you could keep some notes on what helped you = to get started, Andrew, that could become the start of such a document. =2D-=20 John Wiegley GPG fingerprint =3D 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGcBAEBCgAGBQJWgZqXAAoJEMFE2PTxn+YwiysL/ijkxeSpL1ElQFxjJNP2Rg0q dT+KCljwWrgEkY7AuRyzLhABfZmVkPGNPVkcea6si/WGZ1108oNaOZjvHtpB2kFq iXM5sEhwdvq016WvZ6bLk1wgMUgerAM8EhHCqHs3vR2E0dkc/M39BHr5G4UIWJw8 n8bFXG4pbYGjb421EoCGDmXSS34yCj2XQkjBjrqDVU7G9TXBWLWW3ISIcJG4kZmV 1edyUH/KVa5pbBlsSXIssfsSx2+PQOy/I8axkrvfh5mxsgKUQIiQWwyFoZ+3ZdtM HUDTKML/XQSbkLxjrjEPRSmWCJpaMLd4f+652hvXfzHVThpbFoMHuZb1Tmd4rVXu LwCw7w1Xltuxu22GLUqSCZMoV0ZMAatABomNdY0LxYu4NCfRLSHE+r3N3eRWceD/ 7HW5HuStjFr5HromXK/EOuby4ebeBEiB1ISxXfVCav0mQf+Emv7C5eZ/pjfd59zl dgn+oGZJjg3/ggG+Gy4ZKTT30cYEqolnKD3gf8xwJg== =XRm5 -----END PGP SIGNATURE----- --=-=-=--