Morning Stas,

> I think we have to separate FRs and bugs. Bugs filed against older
> versions (especially ones before 5.5) I'd put into feedback with request
> to retest with more recent version. Feedback bugs would automatically
> expire if no feedback was provided.

This sounds reasonable.

> FRs however need more fine-grained approach. Since they are separate
> from bugs, they are easy to filter out and in general may not be
> version-specific. OTOH, having them there, indeed, is not super-useful,
> but is not that harmful either.

The problem with accepting feature requests on bugsnet is that, most of the
time, nobody can implement them because of modern processes.

It's not harmful to us, but it is harmful to the person requesting the
feature, who is probably ignorant of modern processes, and bound to stay
that way until we educate them, or disable feature requests on bugsnet
altogether.

I think I would like to see feature requests disabled on bugsnet, thereby
pushing everyone to use the proper channels (github, internals, RFC's).

What do you think ?

We can still work through existing requests, but the chances of being able
to act on them are slim, and they are just going to sit there for years on
end.

Cheers
Joe


On Sun, Jan 8, 2017 at 9:57 PM, Stanislav Malyshev <smalys...@gmail.com>
wrote:

> Hi!
>
> > I'd even go as far as saying that any bug reported for PHP < 5.6 can be
> > marked as "Won't fix". The bugs targeting 5.6 need to be checked whether
> > they have a security implication and if not they should be also marked
> > as "Won't fix"
>
> Lots of people run 5.5 now. I'd say at least about 2/3 of PHP users in
> the field are now < 5.6. Blanket closing all those bugs with "wontfix"
> sound non-productive to me - I'd rather at least give people chance to
> update the info. Many extension bugs were transferred from 5.x to 7.x as
> is.
>
> --
> Stas Malyshev
> smalys...@gmail.com
>

Reply via email to