Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50547 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8644 invoked from network); 25 Nov 2010 17:24:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 17:24:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 ns.km36107.keymachine.de Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:57856] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/E4-16484-0BB9EEC4 for ; Thu, 25 Nov 2010 12:24:00 -0500 Received: from [192.168.1.29] (ppp-93-104-60-3.dynamic.mnet-online.de [93.104.60.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 92FEB468A6; Thu, 25 Nov 2010 18:23:57 +0100 (CET) To: Derick Rethans Cc: Gustavo Lopes , internals@lists.php.net In-Reply-To: References: <73.C4.59959.876BBEC4@pb1.pair.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 25 Nov 2010 18:23:56 +0100 Message-ID: <1290705836.7033.80.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Hold off 5.4 From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2010-11-25 at 15:11 +0000, Derick Rethans wrote: > > Yes, I also think trunk should be 5.4. It's not the most ideal thing > though, but something we'll have to live with. It's going to be a lot > less of a hassle than cherry picking trunk's features and graft them > onto 5.3. Agreed. Cherry picking from trunk is no option. For being able to do this one either needs feature branches or some strict rules for commit message (for instance "always refer to the relevant RFCs") so one can filter the commits properly. Changing to such a model doesn't belong in a discussion with "5.4" in the subject. johannes