Re: bugsnet cleanup
| From: | Joe Watkins | Date: | Mon, 09 Jan 2017 07:14:15 +0000 |
| Subject: | Re: bugsnet cleanup | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-97614@lists.php.net to get a copy of this message | ||
Morning Kalle,
> I would like some more statuses for the bug tracker
+1 go for it
Cleanup of code/statuses is also desirable ... and you have volunteered to
do it :D
Cheers
Joe
On Mon, Jan 9, 2017 at 6:40 AM, Kalle Sommer Nielsen <kalle@php.net> wrote:
> Morning Joe
>
> 2017-01-09 7:13 GMT+01:00 Joe Watkins <pthreads@pthreads.org>:
> > 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.
>
> For Feature Requests, I agree that we should disable them all together
> on bugsweb, and add a page for redirecting the user to proper channels
> like you mentioned.
>
> Besides this, I would like some more statuses for the bug tracker, or
> maybe rather auto reply/quick fixes instead of having to manually
> copy/paste over and over again. An example could be:
>
> "This extension ($ext) is no longer being actively maintained (Status:
> Suspended)"
>
> Also we got quick fixes for "Try a snapshot (5.4)" and even 5.5!
>
>
>
> --
> regards,
>
> Kalle Sommer Nielsen
> kalle@php.net
>