Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85567 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39428 invoked from network); 30 Mar 2015 20:52:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2015 20:52:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.47 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.47 mail-pa0-f47.google.com Received: from [209.85.220.47] ([209.85.220.47:35313] helo=mail-pa0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DA/04-17871-287B9155 for ; Mon, 30 Mar 2015 15:52:19 -0500 Received: by patj18 with SMTP id j18so21911376pat.2 for ; Mon, 30 Mar 2015 13:52:15 -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=uy1PPG3XmfGirfuSFrjDWoPIBehIu8qkxBgQox85hMY=; b=pNhe/0Oh/6+XAhSO2ODaowwX1/lj2zXdwzigwLa6mIdANJ192G+XCLfi4shbOWdzXq LSQwnsWvoL3hgDfe86hDLnmpYrLjsVbKFLj/qmnazxN50ZMZAtybKceOsIdvGOYDeBF7 puJQV6S1i7RADhQjYYoUznVrjPl2qXPpzbQv3ROpa/zhOV+BVW+FqK58d/MXButvphgj En5WqpypnVIoCxKW0R+Gbn85YTvB3ItNJSsDX/uOA9K6nyvuj1l2X4rq66znk7fmO0sY uUp1V7pJU3bDUjfggOf+YMDWfgVpU7ZJbEBPjJRrP0DQq1Kzxj1gEuvGcMx80EONSYNd Rsow== X-Received: by 10.70.36.198 with SMTP id s6mr6308109pdj.143.1427748735781; Mon, 30 Mar 2015 13:52:15 -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 hs4sm11608216pdb.30.2015.03.30.13.52.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 13:52:14 -0700 (PDT) Message-ID: <5519B77C.5090808@gmail.com> Date: Mon, 30 Mar 2015 13:52:12 -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: Ferenc Kovacs , PHP Internals , Stanislav Malyshev , julien pauli References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: What's our official stance on small self-contained additions in a micro version From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > I know that our official release process allows that, but there are some > reasonable arguments against doing that and this topic was brought up > multiple times related to specific fixes. Adding an option I think it's ok provided it's not controversial and not an attempt to create entirely different large functionality hidden behind the option (e.g. "let's add an option to make mysql_connect also connect to Postgres databases"). If it's something that clearly a small functional piece that is missing, adding it I think is OK. If it's bigger (like entirely new functionality or substantial change in existing one) then it'd be better to go into next version. > I would like to know if we can come up with a rule which can have > consensus behind it, and maybe formalize it as an extension to our > current releaseprocess rfc. I'm not sure there's a formal rule that would be good for all cases. We can have guidelines but unless we reject all changes completely (which I strongly disagree with) I think we'll still have to consider them on the substance. -- Stas Malyshev smalyshev@gmail.com