Re: Re: com php-src: Bug 49898 __getCookies() method implementation: ext/soap/soap.c ext/soap/tests/bug49898.phpt

From: Date: Thu, 19 Jun 2014 20:31:23 +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-75001@lists.php.net to get a copy of this message
On Thu, Jun 19, 2014 at 1: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. Market adoption should be a concern, but I don't think it should be a reason to accept features in patch versions (z in x.y.z). That's my $0.02.

« previous php.internals (#75001) next »