Morning Ferenc, That was a good read, and echos my thoughts in places.
I never intended to do anything without explanation, that would obviously have to be provided. What I was hoping to extract from this conversation is some criteria for the updating of bugs: What we actually consider old, what we consider won't fix, and so on ... Some good ideas have emerged, and I do hope the bug tracker does get the attention it deserves in terms of functionality. People with the power need to do something (that's you :)) to bring the numbers down and focus our efforts, please do so, starting with updating old bugs to feedback status. Cheers Joe On Wed, Jan 18, 2017 at 1:21 PM, Ferenc Kovacs <tyr...@gmail.com> wrote: > > > On Sun, Jan 8, 2017 at 7:46 AM, Joe Watkins <pthre...@pthreads.org> wrote: > >> 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 >> > > hi Joe, > > thanks for triaging the github PRs, I also agree that we should do some > culling on our bugsweb issues (relevant: https://www.joelons > oftware.com/2012/07/09/software-inventory/ ). > just wanted to mention that we have the feedback status, if a bug stays > in the feedback status for 2 weeks the bug will be closed by a cronjob with > the no feedback reason. > we could set the old bugs to feedback with an automatic comment that > please review the issue and target a supported version if you still want > this issue to be resolved and then let the reporters do that or the bug > will be closed. > I think this is a good compromise between just closing/suspending the > issues without explanation. > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu >
