Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50462 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55406 invoked from network); 23 Nov 2010 18:24:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2010 18:24:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain prohost.org designates 209.85.161.42 as permitted sender) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:51814] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/D0-49564-2D60CEC4 for ; Tue, 23 Nov 2010 13:24:18 -0500 Received: by fxm11 with SMTP id 11so1062253fxm.29 for ; Tue, 23 Nov 2010 10:24:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.79.68 with SMTP id o4mr7071318fak.0.1290536654922; Tue, 23 Nov 2010 10:24:14 -0800 (PST) Received: by 10.223.126.199 with HTTP; Tue, 23 Nov 2010 10:24:14 -0800 (PST) In-Reply-To: <1290504719.2294.251.camel@guybrush> References: <1290504719.2294.251.camel@guybrush> Date: Tue, 23 Nov 2010 13:24:14 -0500 Message-ID: To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= Cc: Felipe Pena , internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Release Process From: ilia@prohost.org (Ilia Alshanetsky) 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=FCter : > 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. > > =A0 =A0 =A0 2011 =A0 =A0 =A0 =A02012 =A0 =A0 =A0 2013 =A0 =A0 =A0 =A0 201= 4 =A0 =A0 =A0 =A02015 =A0 =A0 =A0 =A02016 =A0 =A0 =A0 =A02017 > =A0 =A0 =A0 =A0| =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 = =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | > LTS1 =A0 =A0+++++++++++++++++++++++++++++++++++++-----------D =A0 =A0 | = =A0 =A0 | =A0 =A0 | =A0 =A0 | > EA1 =A0 =A0 | =A0 =A0 | =A0 =A0 ++++++++++++D =A0 =A0 | =A0 =A0 | =A0 =A0= | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | > EA2 =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 ++++++++++++D =A0 =A0= | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | > LTS2 =A0 =A0| =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 += +++++++++++++++++++++++++++++++++++-----------D > EA3 =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 |= =A0 =A0 | =A0 =A0 ++++++++++++D > EA4 =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 |= =A0 =A0 | =A0 =A0 | =A0 =A0 | =A0 =A0 ++++++++++++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 > >