Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52722
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 148.87.113.121 cause and error)
Message-ID: <4DE6BE66.3070007@oracle.com>
Date: Wed, 01 Jun 2011 15:34:14 -0700
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>
CC: PHP internals <internals@lists.php.net>
References: <BANLkTim2Tbw+9egfrmrYfeZfNNwYWcg4dg@mail.gmail.com>
In-Reply-To: <BANLkTim2Tbw+9egfrmrYfeZfNNwYWcg4dg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Final version, RFC release process
From: christopher.jones@oracle.com (Christopher Jones)



On 06/01/2011 03:09 AM, Pierre Joye wrote:

> URL: https://wiki.php.net/rfc/releaseprocess

Pierre,

There are some immediately practical things here.  Some things will
be a large jolt for the community and might be better introduced in
future releases.

Chris

Good:
   - Scheduled releases
   - Use of RFCs
   - No PHP script breakages in x.y.z+1 releases

Too complex or not good:
   - Number of concurrent branches: Johannes's suggestion was good
   - Secret voting & automated polls: many things are not binary
     decisions and need discussion
   - Feature preview release: good in theory.  Is there any need to
     formalize this since anyone can create a patch (or fork etc)?

Define & clarify for the lay reader:
   - "External API", "Internal API", ABI, "internals", "userland"


-- 
Email: christopher.jones@oracle.com
Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/