From owner-freebsd-current@freebsd.org Fri Jun 1 10:31:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A27ADEF7817 for ; Fri, 1 Jun 2018 10:31:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6205272BFB; Fri, 1 Jun 2018 10:31:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 87CDA282; Fri, 1 Jun 2018 05:31:51 -0500 (CDT) Date: Fri, 1 Jun 2018 05:31:50 -0500 From: Mark Linimon To: "K. Macy" Cc: "Matthew D. Fuller" , freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180601103150.GB25691@lonesome.com> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> <20180531204946.GB24090@lonesome.com> <20180601032510.GJ11482@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2018 10:31:52 -0000 On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote: > This is where culling older bug reports comes in. Well, even with doing that, the sheer number really doesn't help the S/N that much. It may make someone a bit neurotic like me feel a bit better, but that's all. > However, when I've tried wading through the bug system to find things > that I might be able to fix, I have not found it easy at all. To me, reasoning about 'search' is the riqht direction to go. (Apologies to folks for the long URLs, but I would rather not hide the search terms here.) We've been inconsistent about applying the 'patch-ready' tag to indicate something is ready to go, but here's the current list for the Base System: https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=patch-ready&keywords_type=allwords&list_id=232422&product=Base%20System&query_format=advanced&resolution=--- 8 bugs. Not that bad. The 'patch' tag by itself produces a much less satisfying result: https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=patch&keywords_type=allwords&limit=0&list_id=232422&order=bug_id%20DESC&product=Base%20System&query_format=advanced&resolution=--- 600 bugs. Moderately overwhelming. Narrowing it down to just the 'kern' component only helps a little: https://bugs.freebsd.org/bugzilla/buglist.cgi?component=kern&keywords=patch&keywords_type=allwords&list_id=232433&product=Base%20System&query_format=advanced&resolution=--- 300 bugs. Looking for tag 'regression' within that is more satisfying: https://bugs.freebsd.org/bugzilla/buglist.cgi?component=kern&keywords=regression&keywords_type=allwords&list_id=232433&product=Base%20System&query_format=advanced&resolution=--- 82 bugs. tl:dr; expecting any sane person to 'browse' thousands of entries of any kind from _any_ kind of list, is itself madness. OTOH myself, and koobs and others, are willing to work on the search metadata to at least make 'search' reasonable. [obv. disclaimer: I am only citing statistics for Bugzilla here, not Phabricator; I simply know it better.] mcl