Newsgroups: php.internals,php.internals Path: news.php.net Xref: news.php.net php.internals:97628 php.internals:97629 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80232 invoked from network); 9 Jan 2017 16:10:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jan 2017 16:10:45 -0000 X-Host-Fingerprint: 217.240.243.255 pD9F0F3FF.dip0.t-ipconnect.de Received: from [217.240.243.255] ([217.240.243.255:27279] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/DB-31343-206B3785 for ; Mon, 09 Jan 2017 11:10:43 -0500 To: internals@lists.php.net,Joe Watkins , References: Message-ID: Date: Mon, 9 Jan 2017 17:10:38 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 170109-1, 09.01.2017), Outbound message X-Antivirus-Status: Clean X-Posted-By: 217.240.243.255 Subject: Re: bugsnet cleanup PHP internals From: info@stricted.net (Jan Altensen) Am 08.01.2017 um 07:46 schrieb Joe Watkins: > Morning internals, > > Some of you may have noticed that a few of us have put considerable effort > into cleanup of pull requests on github, these are now manageable and I'm > quite confident that we will be able to merge pull requests in a timely > manner, and stay on top of it. > > When it comes to bugsnet, there are feature requests and bugs that have > been open for more than 10 years, and nobody has talked about them in about > as long, they may concern defunct versions of PHP, or removed extensions or > SAPIs: These numbers in the thousands. > > It's very difficult (impossible) to see a good reason for these to be open, > they are not useful at all. > > With normal support for 5 ended, now is the perfect time to cleanup > bugsnet. If we can get the numbers down to something manageable, we have a > reasonable expectation to stay on top of them. > > I think anyone that has been waiting a number of years for a response to a > feature request deserves to know that it is not reasonably happening, and > that there are better ways of trying to get a feature in than opening > yet-another-feature-request on bugsnet. > > I think any bug report opened against 4 and not updated is useless. > > I think anything with a patch attached targeting 5 is useless, regardless > of age; they should be encouraged to open a pull request on github against > a supported branch. > > I'd like to hear what others think about cleaning up bugsnet, what criteria > we might use for a mass cleanup. > > After a mass cleanup, I/we will go in and start working through whatever is > left, but 5k mostly irrelevant bugs is too much to ask, it would take me > months and months to work through those, time that nobody has, or will ever > have. > > Cheers > Joe > +1 from me i would help cleaning up but im not familiar with the bugsnet system :/