From owner-freebsd-current@freebsd.org Thu May 31 20:49:49 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 1E25CEF7E5F for ; Thu, 31 May 2018 20:49:49 +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 B8F6E7E739; Thu, 31 May 2018 20:49:48 +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 C26CEE38; Thu, 31 May 2018 15:49:47 -0500 (CDT) Date: Thu, 31 May 2018 15:49:46 -0500 From: Mark Linimon To: Joe Maloney Cc: Daniel Eischen , Konstantin Belousov , Johannes Lundberg , freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180531204946.GB24090@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> 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: Thu, 31 May 2018 20:49:49 -0000 Straying off-topic from the Subject line ... On Thu, May 31, 2018 at 11:34:18AM -0400, Joe Maloney wrote: > Technically since I was using PC-BSD, and was a committer for that > project I had no real dire need to reach out to FreeBSD about the > [wireless driver issue]. I was simply trying to help anyone else > who might be encountering the same issue trying to use stock FreeBSD > because it was a simple backport. If my effort had turned out to be > more fruitful I would have spent more time pursuing tickets, diffs, > or whatever to get more things back-ported when I found them. FreeBSD doesn't do well handling problem reports. We've known it for years but no one has come up with a magic solution yet. We have volunteers willing to triage, but not enough committers willing to suspend working on their own priorities to work through the backlog. (It's understandable, really.) And the backlog is astounding. (*) I hesitate to even look, but ... kern 3270 ports 2010 bin 1607 The flow has decreased from where it was a few years ago -- this stat says that 727 total new ones have come in this month. We do slightly better turning over ports PRs -- due to the fact that we attach a maintainer field to each port. This doesn't completely solve the problem, but it goes some distance. Finally, the number of PRs with patches stands around 1021. That is particularly disappointing. Well, it's too bad we weren't able to corral you into keeping working on such things. fwiw. mcl *: there are other categories but these constitute the majority (9485 in total).