Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58464 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22113 invoked from network); 2 Mar 2012 09:26:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 09:26:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.42 mail-qw0-f42.google.com Received: from [209.85.216.42] ([209.85.216.42:41005] helo=mail-qw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/88-11220-A52905F4 for ; Fri, 02 Mar 2012 04:26:51 -0500 Received: by qaui11 with SMTP id i11so163468qau.8 for ; Fri, 02 Mar 2012 01:26:48 -0800 (PST) Received-SPF: pass (google.com: domain of tyra3l@gmail.com designates 10.224.218.10 as permitted sender) client-ip=10.224.218.10; Authentication-Results: mr.google.com; spf=pass (google.com: domain of tyra3l@gmail.com designates 10.224.218.10 as permitted sender) smtp.mail=tyra3l@gmail.com; dkim=pass header.i=tyra3l@gmail.com Received: from mr.google.com ([10.224.218.10]) by 10.224.218.10 with SMTP id ho10mr6606217qab.16.1330680408420 (num_hops = 1); Fri, 02 Mar 2012 01:26:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4UwIIbU8Q0mJ6dlMAwtHzONwcaF6Sugyw3cfKYTi6qM=; b=Jy43jup+t3bNkT8BfjfOi0C4ySBJshAM0kxny1ZNJK18EqEhosDhkTxvTdha17px7N rBp0/6Z04BEY9ZnfHlnQVpBf4MoPKrgKLGnSLplOWn1q9U2RxnixNhzDNtA1alQrO9h8 KpvbmjnOHVxIrvXUl/5FRHqJWwJmo630KCYJd6+CO+hT13jYFlBzyIi/lDbyuS/7eW6n vGUY/psGuH7v6OeNQEhrq+M1x3MW8vtFDCgvWkLHkaof3tg8XS/q1/+BkjwQIjO5cP5W /2dwACHoUroVexfIMp1pCxoMUkrKM7U3zmgBWf0ZS+ePRMReS0xclmbtJQeEqqeNb8nS z0ug== MIME-Version: 1.0 Received: by 10.224.218.10 with SMTP id ho10mr5547166qab.16.1330680408351; Fri, 02 Mar 2012 01:26:48 -0800 (PST) Received: by 10.229.232.207 with HTTP; Fri, 2 Mar 2012 01:26:48 -0800 (PST) In-Reply-To: References: Date: Fri, 2 Mar 2012 10:26:48 +0100 Message-ID: To: David Soria Parra Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=20cf300fad4f0ca4a404ba3f2dca Subject: Re: [PHP-DEV] HEADS UP: 5.4 branch is open again From: tyra3l@gmail.com (Ferenc Kovacs) --20cf300fad4f0ca4a404ba3f2dca Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Mar 2, 2012 at 1:33 AM, David Soria Parra wrote: > Hi internals, > > just a heads up. The PHP_5_4 branch is open for commits again. > > - David > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > On a somehow related topic: Now that we have 5.4 out, I have a question: Do we know what will be the next major release? If we want to follow the releaseprocess RFC, I think it would be nice to think about whether we plan to roll out a major or a minor version next. By the RFC, we can't do such changes to the language as we did with 5.2->5.3 or 5.3->5.4, because userland BC breaks aren't allowed. So I can see two way to address this: If we can agree upon the next version number beforehand, and we decide that we will go with the major release (be that php 6 or 7, whatever), we don't to do anything right now, we can branch the version from trunk/master, when the time comes. If we can't agree upon the next version number, or we agree upon that there will be an 5.5 version, I think it would make sense to create a branch for it ASAP, so there is place (trunk/master) for the approved but backward incompatible changes, and people don't have to hold patches. What do you think? --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --20cf300fad4f0ca4a404ba3f2dca--