Re: [PHP-DEV] Re: PHP 5.6 life cycle

2015-12-14 Thread Yasuo Ohgaki
Hi all, On Tue, Dec 15, 2015 at 8:43 AM, Stanislav Malyshev wrote: > >> Furthermore, postponing EOL now means reduced pressure to upgrade to 7. > > Again, if you think people's decision to upgrade significantly depends > on that, I think you are deluding yourself. We have tons of "pressure" > to

Re: [PHP-DEV] Re: PHP 5.6 life cycle

2015-12-14 Thread Lester Caine
On 14/12/15 23:43, Stanislav Malyshev wrote: > I'm not sure what you mean here by "should be". If you mean "if > everybody dropped everything right now and started only working on > upgrade to PHP 7 then they could make it in 20 months" - yes, it is > reasonably true. But nobody would do that. In f

Re: [PHP-DEV] Re: PHP 7.0.1 scheduling

2015-12-14 Thread Stanislav Malyshev
Hi! > Why not use RC2 as a chance for some security patches to get tested ? > If we have a RC2 (which is not bad IMO, we have a time slice here at > end of 2015 that enables us to release an RC2) , we then could merge > into this one some well-selected security patches, f.e, some t

Re: [PHP-DEV] Re: PHP 5.6 life cycle

2015-12-14 Thread Stanislav Malyshev
Hi! > That means 5.6 EOL is 20 months and 11 days away. That's more than one > and a half years, it should be enough time to upgrade. I'm not sure what you mean here by "should be". If you mean "if everybody dropped everything right now and started only working on upgrade to PHP 7 then they could

[PHP-DEV] Benchmark Results for PHP Master 2015-12-14

2015-12-14 Thread lp_benchmark_robot
Results for project PHP master, build date 2015-12-14 11:28:47+02:00 commit: 0ec58fa32bb9794c913e17f53857c9b08bea6ee7 revision date: 2015-12-14 09:15:36+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB mem