Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85674 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89154 invoked from network); 1 Apr 2015 20:37:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2015 20:37:01 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.173 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.173 mail-pd0-f173.google.com Received: from [209.85.192.173] ([209.85.192.173:36273] helo=mail-pd0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 34/7D-21906-BE65C155 for ; Wed, 01 Apr 2015 15:37:00 -0500 Received: by pdea3 with SMTP id a3so14768717pde.3 for ; Wed, 01 Apr 2015 13:36:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bkprKRKndANMeZD6bGMStxRbelqFttnisdULIHN6LyI=; b=aJmoWLT9vk8dkYPCWXbfFg64iDlylolITVc3qRo6R61eFHV6Y8vv3l9K6Oap/PbS4n wNuuwevjevbs62SXf9V8ssr8sxkSd42ROY1Y+GgOkaKdnTBQFtjCLDs+c8ut553YI+EB vIDCftpjufLaZuwMi9y0DmR/WlIlo4WoR8eRDECH/F6sOzfx4bK9sY8G5Pn5/4VNT2jh zZjGOsuAIS+G+AwFf+NR84r1eXB0DqpHrx1dcTdF24EBzNlhDXk/+DMfRiz9IY8swsqE dH6GAI/reecsu/fRyzrCRLp5JCnrbH0GCqLhgo6saDsbXUrDfEXZv/jyLGtMFOq4o9DP 43Pw== X-Received: by 10.66.235.169 with SMTP id un9mr78956669pac.45.1427920616838; Wed, 01 Apr 2015 13:36:56 -0700 (PDT) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id hs8sm2971338pbc.79.2015.04.01.13.36.54 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Apr 2015 13:36:56 -0700 (PDT) Message-ID: <551C56E2.8090100@gmail.com> Date: Wed, 01 Apr 2015 13:36:50 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Dennis Birkholz , internals@lists.php.net References: <551BC7CF.3080309@birkholz.biz> <551C44C7.6060108@gmail.com> <551C48AC.3090908@birkholz.biz> <551C4A60.2050805@gmail.com> <551C5045.3010405@birkholz.biz> In-Reply-To: <551C5045.3010405@birkholz.biz> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What's our official stance on small self-contained additions in a micro version From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Debian, Ubuntu and CentOS: ~21,23% > > (I assume here like Anthony that the installs matching a distribution > specific version always come from that distribution). Pretty big one, I'd say, but even with this one you only get 1/5. Also, as I said, it's very easy to take distro package and repackage it to use the source from the same minor but up-to-date patch version. > An addition and a bug fix are different things. I know but you said, I'm quoting, "please let the x.y.z versions contain only additional (security) fixes" which excluding non-security fixes too. Let's consider a somewhat arbitrary example: https://github.com/php/php-src/pull/1211 There's a HTTP status code needs to be added (doesn't matter if new or just omitted by oversight). You could have it in next 5.6 version (you can have it in use in 3 months realistically - one month for release to catch up, 2 months for ops in your project to be confident that new patch release doesn't break anything) or you could have it in 2.5 years (1.5 years for 7.1 to be released, 1 year - and that's *extremely* optimistic - for ops to be ok to switch to a new distro version which hopefully - just hopefully, extremely optimistic again - but that time ships with 7.1 and not still randomly patched 5.5). For me, it sounds insane that you'd have to wait for so long for such a simple thing. Of course, instead of status code it could be option support in XML, or new function/option support in ICU, or new connection option in mysql. Any improvement in the environment - do you want it in PHP in terms of several years or in terms of 3 months? I foresee what it would turn into is arguing "well, not supporting option X is really a bug so that's a bugfix!" which only will lead to more chaos and argument. -- Stas Malyshev smalyshev@gmail.com