Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52734 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31398 invoked from network); 2 Jun 2011 05:32:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jun 2011 05:32:30 -0000 Authentication-Results: pb1.pair.com header.from=peter.e.lind@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=peter.e.lind@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: peter.e.lind@gmail.com X-Host-Fingerprint: 74.125.83.42 mail-gw0-f42.google.com Received: from [74.125.83.42] ([74.125.83.42:49884] helo=mail-gw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/43-32367-C6027ED4 for ; Thu, 02 Jun 2011 01:32:29 -0400 Received: by gwb17 with SMTP id 17so250888gwb.29 for ; Wed, 01 Jun 2011 22:32:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Zay1WEqbSB3/mNJowu+gINWdXBlNLfQbzKo77R6lxfQ=; b=vJXnnoJ6lRxA8V2CWF0OWgKIQGxO1Jf2ZpfxI8PU/ldkMIIXPyE5DWOqpRM96+4t2y SHFKR5k/3iXenUWT2hdQiwOlLMp05svduVGNPnZu1X1wQn/aQkEPkkq3SPu/O9/Zj1k2 5YpA5vE40X7FWkjkw8FTy2uSEPvDXG+sVeE50= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KFV0TRngsYh5yLOZxb9IYM9RkLGPCpyC/m5CLXNmvN4pBDgc/6WDvleF11RrCvgNJ0 EtVnFLVP/FxpZqfeX0IIHcPqXJiLSgCZzla7mXZxDJD16t/cYeOenkIE9jBjru3kS9Z7 ziJR0PUlOlWYLAi6zcuDx1K5qWPoYvHPUIR0Y= MIME-Version: 1.0 Received: by 10.91.212.15 with SMTP id o15mr258362agq.189.1306992746381; Wed, 01 Jun 2011 22:32:26 -0700 (PDT) Received: by 10.90.33.19 with HTTP; Wed, 1 Jun 2011 22:32:26 -0700 (PDT) Received: by 10.90.33.19 with HTTP; Wed, 1 Jun 2011 22:32:26 -0700 (PDT) In-Reply-To: References: <4DE6BE66.3070007@oracle.com> Date: Thu, 2 Jun 2011 07:32:26 +0200 Message-ID: To: Pierre Joye Cc: Christopher Jones , PHP internals Content-Type: multipart/alternative; boundary=00163645849e5f3fea04a4b3f6ad Subject: Re: [PHP-DEV] Final version, RFC release process From: peter.e.lind@gmail.com (Peter Lind) --00163645849e5f3fea04a4b3f6ad Content-Type: text/plain; charset=UTF-8 On Jun 2, 2011 12:46 AM, "Pierre Joye" wrote: > > hi Chris > > On Thu, Jun 2, 2011 at 12:34 AM, Christopher Jones > 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. > Sorry for jumping into the thread, but I couldn't help noting that you seem confused about the distro suggestion. I think Ubuntu was the example, and there's nothing random at all about their release process. There are fixed timelines and life cycles in Ubuntu - having less branches does not in any way stop them from having a fixed release process and schedule. Regards Peter --00163645849e5f3fea04a4b3f6ad--