Re: Final version, RFC release process

hi Chris On Thu, Jun 2, 2011 at 12:34 AM, Christopher Jones <christopher.jones@oracle.com> wrote: > > > 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 This proposal for distros not for programming languages or similar tools. All users I talk to need fixed timeline, life cycle, etc. to have a clear and plan-able way to deal with php versions. >  - Secret voting & automated polls: many things are not binary >    decisions and need discussion There is no secret voting. >  - Feature preview release: good in theory.  Is there any need to >    formalize this since anyone can create a patch (or fork etc)? Yes, just to explain what it is and tell devs they can do it and (< that's important) publish it. > Define & clarify for the lay reader: >  - "External API", "Internal API", ABI, "internals", > "userland" On it :) -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org