On Mar 3, 2015 4:31 AM, "Julien Pauli" <[email protected]> wrote:
> Same to me, I voted no because we're gonna break something which is not
> "that bad" and turn it to a clear breakage in one step.
> I would prefer we E_DEPRACTE before E_ERRORing , we can deprecate in 7.0
> and remove in 7.1 or 7.2 or whatever.
> We chose not to have a 5.7 for deprecation purpose only (or not), but this
> doesn't mean 7.0 shouldn't deprecate anything IMO.
We should not remotely consider to remove things like that in 7.x, ever.
This will simply make applications migration to latest 7 series a nightmare.
And yes, I do consider it was a strategical mistake to have rejected 5.7
for this exact reason. Same for the random features freeze deadline, we end
up now with so many decisions to take on a hurry, while many of them are
critical for 7.
Both should be reconsidered. I do not think that will affect the final
release date for 7.