2014-01-31 Pierre Joye <pierre.php@gmail.com>:
> On Fri, Jan 31, 2014 at 12:29 PM, Derick Rethans <derick@php.net> wrote:
> > On Fri, 31 Jan 2014, Stephen Zarkos wrote:
> >
> >> From: Hannes Magnusson [mailto:hannes.magnusson@gmail.com]
> >>
> >> > I was hoping for yes/no vote - which case I would have voted +1 and
> >> > we could work on better approach for the extensions in time for the
> >> > 6.0 release which this clearly is the start of.
> >>
> >> Two years from the release of 5.6.0, 5.5 will be EOL and extension
> >> developers can just focus on compat with 5.6+ and 6.0 (assuming we
> >> ever see it). At that time it would be nice IMHO if 5.6+ and 6.0 were
> >> as similar as possible, starting with this RFC.
> >
> > EOL in userland has no meaning. With many distributions on PHP 5.3 or
> > 5.4, and commercial users even older version (we have to maintain 5.2
> > support for now f.e.) it's really not as simple as saying that "when 5.5
> > is EOL, we can just focus on 5.6+ and 6.0. This is not Utopia.
>
> It was always like that. It was the case from 4.x to 5.x, and many of
> us use that argument to block must have features in 5.0. Interestingly
> enough we added every single features afterwards... Go figure.
>
>
> In short: we are upstream and we have to focus on moving forward and
> keep PHP as its best possible level. That does not mean we have to
> break things in every single release but we cannot stick to something
> because we have to support the last 5 dead major releases for some
> random customers, who rely on distributions anyway (they won't update
> using upstream code any time soon anyway).
>
> cheers,
> --
> Pierre
>
This. Said even better than I was planning to.