Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52724 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55561 invoked from network); 1 Jun 2011 22:46:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 22:46:17 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-ww0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:57372] helo=mail-ww0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/A9-32367-831C6ED4 for ; Wed, 01 Jun 2011 18:46:16 -0400 Received: by wwk4 with SMTP id 4so4197233wwk.5 for ; Wed, 01 Jun 2011 15:46:13 -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 :content-transfer-encoding; bh=Xb1V4PIcOsoo8NXdRGODf74jnc7lSBhlVJc4OnZ/VU8=; b=OeQ6VehkOUSkp0Z/i49GGr72Yag+OFrIkvBQV/ewwF9FvLA4E5t1La7AEF7p6+7elI Df6MDwjmep6mbukFP+PCLz5FeBlpqQsDWj1Up2Qk7zgy2vSFWGaKJoIVHhcjCspQ8XTf JDyS8QJlNmA2zYraEvlQdNf8fWuixYttIJsLQ= 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:content-transfer-encoding; b=KrGPt8LG2AC3zRqbKZNJMtzzlA4B9khTdQRz5JSGzXlZdO9lPn3d0StHai1CC+1tjy 3YtDQTRZy5zPOPOTuy4Dk9PKq89PZ0kh+6oItll0EB8+ApOAYttJ3gboJaNsvUmd+i57 xgVh6xxFfxc/+n0RljZbaEEogzyP1n9uzIFc8= MIME-Version: 1.0 Received: by 10.216.15.137 with SMTP id f9mr25420wef.62.1306968373322; Wed, 01 Jun 2011 15:46:13 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Wed, 1 Jun 2011 15:46:13 -0700 (PDT) In-Reply-To: <4DE6BE66.3070007@oracle.com> References: <4DE6BE66.3070007@oracle.com> Date: Thu, 2 Jun 2011 00:46:13 +0200 Message-ID: To: Christopher Jones Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Final version, RFC release process From: pierre.php@gmail.com (Pierre Joye) 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. =A0Some things will > be a large jolt for the community and might be better introduced in > future releases. > > Chris > > Good: > =A0- Scheduled releases > =A0- Use of RFCs > =A0- No PHP script breakages in x.y.z+1 releases > > Too complex or not good: > =A0- 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. > =A0- Secret voting & automated polls: many things are not binary > =A0 =A0decisions and need discussion There is no secret voting. > =A0- Feature preview release: good in theory. =A0Is there any need to > =A0 =A0formalize 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: > =A0- "External API", "Internal API", ABI, "internals", "userland" On it :) --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org