Re: Final version, RFC release process
| From: | Christopher Jones | Date: | Wed, 01 Jun 2011 22:34:14 +0000 |
| Subject: | Re: Final version, RFC release process | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-52722@lists.php.net to get a copy of this message | ||
On 06/01/2011 03:09 AM, Pierre Joye wrote:
URL: https://wiki.php.net/rfc/releaseprocessPierre, 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/