On 14/06/2016 20:43, Stanislav Malyshev wrote:
And I'm not sure how rushing 8.0 helps anything if you're afraid of breaks - you get useful features later but also bigger breaks. Long term it doesn't matter anyway unless 7.1 is somehow special, which is not. Also, having just two minor versions seems to be a little thin, unless there's a plan to keep maintaining 7.x, in which case the question is - who's going to do that?
In my mind, it's not a case of "rushing 8.0"; it's looking at what features we want to release, and how to group and label them.
There seems to be an implication here that if we said we were labelling a release 8.0, we'd be *obliged* to break things in it, rather than just *allowed* to break them, which makes no sense to me. We're not going to run out of version numbers by using them up too quickly.
I think this is where a road map would come in handy; nothing fancy, just a list of things that are waiting to get into a release, and maybe a general "theme" for each release. If there are lots of small but breaking changes coming up, they could be grouped into a release, which we would label 8.0. If we want those changes to get released quickly, then that release would be soon.
The only difference over drip-feeding them into the 7.x series would be that users would know when to expect things to break.
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
