Re: Re: com php-src: Bug 49898 __getCookies() method implementation: ext/soap/soap.c ext/soap/tests/bug49898.phpt
| From: | Pierre Joye | Date: | Fri, 20 Jun 2014 05:53:21 +0000 |
| Subject: | Re: Re: com php-src: Bug 49898 __getCookies() method implementation: ext/soap/soap.c ext/soap/tests/bug49898.phpt | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-75015@lists.php.net to get a copy of this message | ||
On Jun 19, 2014 9:59 PM, "Stas Malyshev" <smalyshev@sugarcrm.com> wrote:
>
> Hi!
>
> > Reading this post tells me exactlt why new features should go in x.y+1.
It
> > is a pain to figure which point versions introduced which features.
Always
> > was.
>
> You seem to be ignoring the fact that 5.5 is adopted by less than 10% of
> the market. This means if we say new features go only into 5.6, even
> minor ones like adding an obvious function, that is essentially saying
> to the vast majority of users "if you submit a pull now, you's probably
> get to use it about 2-3 years from now". It's not what people expect
> from an actively used open-source project, I think.
Adoption suffers more from BC breaks and backport of features.
Even if BC breaks are much more rare, our users still think there are too
many.
No BC breaks and new appealing features improve early adoption.
This is what I hear out there and what I explain to customers not willing
to move to recent versions.