Re: [RFC] Release Process

I think support 5 or even 3 parallel versions will be highly impractical and extra-ordinarily challenging. I think we need a plan that limits us to 2 versions and perhaps a 3rd one for critical security fixes only. 2010/11/23 Johannes Schlüter <johannes@schlueters.de>: > Hi, > > On Mon, 2010-11-22 at 23:21 -0200, Felipe Pena wrote: >> With the recent chaos in the way we begin and ended releases, we would >> like to propose a clean way to deal with releases and related decisions: [1] > > Thanks for preparing this. I have one change proposal: > > With the proposed model it might, as you have illustrated, happen that > there are 5 versions being maintained. > > As I mentioned multiple times on this list, on irc and other places I > like a Ubuntu-like model with two kinds of release which I, for the > purpose of this discussion, call "early access" (EA) and "long term > supported" (LTS) version. > > At any given time only one EA may exist. When a new LTS version is being > released the previous LTS version enters security-only mode to give > users a transition period. Between every LTS version there are two EA > versions. > >       2011        2012       2013         2014        2015        2016   >      2017 >        |     |     |     |     |     |     |     |     |     |     |   >   |     | > LTS1    +++++++++++++++++++++++++++++++++++++-----------D     |     |     |     | > EA1     |     |     ++++++++++++D     |     |     |     |     |     |     | >     | > EA2     |     |     |     |     ++++++++++++D     |     |     |     |     | >     | > LTS2    |     |     |     |     |     |     > ++++++++++++++++++++++++++++++++++++-----------D > EA3     |     |     |     |     |     |     |     |     ++++++++++++D > EA4     |     |     |     |     |     |     |     |     |     |     > ++++++++++++D > > The benefit is that developers and users who require a specific feature > get it early while distributors/hosters/software vendors/... have a safe > bet. > > johannes > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >