Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97856
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAL=_i_nuF0y8TC_GrWsX5e77sP-jKq+ed374SW0e=VxSPniVjg@mail.gmail.com>
References: <CAL=_i_nuF0y8TC_GrWsX5e77sP-jKq+ed374SW0e=VxSPniVjg@mail.gmail.com>
Date: Wed, 18 Jan 2017 14:21:05 +0100
Message-ID: <CAH-PCH7M3SVcyxS3owa-zF5nvHOkC1Q84JixODs_6=h34gF1Gw@mail.gmail.com>
To: Joe Watkins <pthreads@pthreads.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c13057207c3ce05465e4af7
Subject: Re: [PHP-DEV] bugsnet cleanup
From: tyra3l@gmail.com (Ferenc Kovacs)

--94eb2c13057207c3ce05465e4af7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 8, 2017 at 7:46 AM, Joe Watkins <pthreads@pthreads.org> wrote:

> Morning internals,
>
> Some of you may have noticed that a few of us have put considerable effor=
t
> 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 abo=
ut
> 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 ope=
n,
> 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 agains=
t
> a supported branch.
>
> I'd like to hear what others think about cleaning up bugsnet, what criter=
ia
> 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 ev=
er
> 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.
joelonsoftware.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.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--94eb2c13057207c3ce05465e4af7--