Re: Are feature request bugs ever looked at?
| From: | Dmitri Dmitrison | Date: | Sun, 06 May 2012 15:23:00 +0000 |
| Subject: | Re: Are feature request bugs ever looked at? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-60495@lists.php.net to get a copy of this message | ||
On Sun, May 6, 2012 at 10:38 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>
> We don't have the resources to go through and thoroughly evaluate each
> feature request. A couple of developers will read each one and if it
> resonates with them personally they will do something about it.
> Otherwise they leave it for another developer to address later.
>
> Some numbers. We have had 2899 feature requests submitted. Out of these,
> 605 are still open. 1134 have been implemented. 705 rejected because
> they weren't valid features. 322 rejected as "Won't fix" for various
> reasons. The rest are in various other states such as Duplicate, and
> awaiting feedback. So feature requests do get processed eventually.
>
> -Rasmus
That is actually a promising statistic.
However, is there a predictable process for picking some requests over others?
If it's based on whether it resonated with the PHP dev who happened to
look at it, why even have a voting feature (and suggest that it
somehow affects the bug's priority)?
I understand this is a free software project, and that resources are
limited. And that you can't force contributors to work on features
they don't personally like.
But I would have expected the bugs with hundreds of votes and/or
comments to be inspected first... Or at least after 10 years... Am I
being unreasonable?
On Sun, May 6, 2012 at 11:07 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> Just a quick reply from my phone:
> anybody can register a wiki account and anybody can get rfc karma after
> sending a mail to the php-webmaster mailing list (this is a basic spam
> protection).
> about the rfc vs bug tracker: the wiki and the rfc process came later than
> the bugtracker.
> I would open a feature request ticket if I don't know how to proceed further
> or I don't have the time to create and push an RFC. Otherwise I would go
> with an rfc: albeit it requires more work from the reporter but makes up for
> it because it provides much bigger visibility and guranteed response from
> the developers.
Thank you, that makes more sense to me.