Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47481 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71303 invoked from network); 23 Mar 2010 16:22:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 16:22:00 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 72.14.220.155 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 72.14.220.155 fg-out-1718.google.com Received: from [72.14.220.155] ([72.14.220.155:50757] helo=fg-out-1718.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5A/50-03444-6AAE8AB4 for ; Tue, 23 Mar 2010 11:21:59 -0500 Received: by fg-out-1718.google.com with SMTP id 22so1312437fge.11 for ; Tue, 23 Mar 2010 09:21:55 -0700 (PDT) Received: by 10.87.8.4 with SMTP id l4mr3439547fgi.1.1269361315468; Tue, 23 Mar 2010 09:21:55 -0700 (PDT) Received: from [192.168.200.22] (c-98-234-184-167.hsd1.ca.comcast.net [98.234.184.167]) by mx.google.com with ESMTPS id 13sm4948177fxm.2.2010.03.23.09.21.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 23 Mar 2010 09:21:53 -0700 (PDT) Message-ID: <4BA8EA9C.7030307@lerdorf.com> Date: Tue, 23 Mar 2010 09:21:48 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100321 Shredder/3.0.5pre MIME-Version: 1.0 To: Pierre Joye CC: Derick Rethans , PHP Developers Mailing List References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] trunk is alive and open From: rasmus@lerdorf.com (Rasmus Lerdorf) On 03/23/2010 09:11 AM, Pierre Joye wrote: > hi, > > I would rather have some kind of rules defined before opening trunk > again (or the pandora box). That's what we are discussing right now. > May I know why you choosed that now is the right time to do it and > declare it open? We have rules. Large features, write an RFC and we discuss it. Small and obvious improvements follow commit-then-review as before. We don't need more complicated rules than that. -Rasmus