Hi all.

Am 08.01.17 um 11:29 schrieb Nikita Popov:
> On Jan 8, 2017 7:47 AM, "Joe Watkins" <pthre...@pthreads.org> wrote:
> 
> Morning internals,
[…]
> 
> 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 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"

There might be issues that are still relevant, but IMHO it's easier to
reopen an issue when need arises than investing the manpower of checking
whether that's still an issue with PHP 7 or not.

Just my 0.02 €

Andreas

PS: Ping me when I shall give a hand at that task!

-- 
                                                              ,,,
                                                             (o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl                                                       |
| mailto:andr...@heigl.org                  N 50°22'59.5" E 08°23'58" |
| http://andreas.heigl.org                       http://hei.gl/wiFKy7 |
+---------------------------------------------------------------------+
| http://hei.gl/root-ca                                               |
+---------------------------------------------------------------------+

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to