> -----Original Message----- > From: a...@adamharvey.name [mailto:a...@adamharvey.name] On > Behalf Of Adam Harvey > Sent: Wednesday, December 17, 2014 12:10 AM > To: Zeev Suraski > Cc: PHP Internals > Subject: Re: [PHP-DEV] [RFC] PHP 5.7 > > On 16 December 2014 at 14:00, Zeev Suraski <z...@zend.com> wrote: > >> - We cannot patch 5.6 to add any Warnings-of-any-kind (stable > >> release, under release process that forbids that) > > > > What part of the release process forbids that? > > None, but I'd still advocate releasing a new minor because there's plenty > of > anecdata suggesting that our userbase tend to consider 5.x.y and 5.x.y+z > to > be the same in terms of features. We used to see this confusion in ##php a > lot over things like crypt() algorithm support changing over the course of > 5.3: > trying to explain that you don't want to use anything before 5.3.7 is > actually > surprisingly difficult, whereas saying "5.4 fixes this" is easy.
I actually agree with that. My view, though, that if we think that delivering those deprecation messages is critical, we're facing a choice between two less-than-ideal options. The 5.7 option defeats the purpose for which it's built - getting a substantial number of people to upgrade and see those messages in the first place. It'll also create an awkward and maybe even silly situation where we'd have two active versions - both with its own monthly releases, but effectively virtually identical to each other in every regard except for these messages. Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
