Scott Arciszewsk, I read the 8 month suggestion that someone else brought up. I do not recall who brought it up, but I think 2017 is far too much time. It only further enables bad practices.
Jan Ehrhardt, That is not PHP's responsibility, that is your responsibility to update your own code. No one is going to force you to update, but it should not be PHP Development's strance to further enable people to use old code. On Sun, Dec 6, 2015 at 7:38 PM, Scott Arciszewski <sc...@paragonie.com> wrote: > On Sun, Dec 6, 2015 at 7:33 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > > > Adam Howard in php.internals (Sun, 6 Dec 2015 18:07:53 -0500): > > >8 months is fine. It is more than enough time for people to upgrade and > > >adapt. > > > > It ain't. If you have got large sites that are built with a framework > that > > requires an older PHP-version you will have to (a) convince the site > owner > > that an upgrade is absolutely necessary, (b) agree on the functional > specs > > of the site after the upgrade, (c) agree on a price quote with the > content > > owner, (d) get that quote accepted by the purchase department of the site > > owner. Each of these steps can easily take several months and then you > are > > not even starting building. > > -- > > Jan > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > Where did this 8 months figure come from? > > PHP 7.0.0 available -> 2015-12-03 > > Today -> 2015-12-06 > > PHP 5.6.x EOL'd -> 2017-08 > > That's more than 8 months. > > Scott Arciszewski > Chief Development Officer > Paragon Initiative Enterprises <https://paragonie.com/> >
