Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49391 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31855 invoked from network); 11 Aug 2010 22:14:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2010 22:14:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.123 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.123 smtp123.iad.emailsrvr.com Linux 2.4/2.6 Received: from [207.97.245.123] ([207.97.245.123:40470] helo=smtp123.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/99-18548-DC0236C4 for ; Wed, 11 Aug 2010 18:14:37 -0400 Received: from relay32.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay32.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 68B1B1B40B1; Wed, 11 Aug 2010 18:14:34 -0400 (EDT) Received: by relay32.relay.iad.mlsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 2886B1B4084; Wed, 11 Aug 2010 18:14:34 -0400 (EDT) Message-ID: <4C6320C9.5060306@sugarcrm.com> Date: Wed, 11 Aug 2010 15:14:33 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 MIME-Version: 1.0 To: Pierre Joye CC: PHP Internals References: <4C62EC4A.9020106@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] back to 5.4 alpha From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I think using trunk as base is a mistake. We should begin using a > stable branch (5.3) and merge what we want for the next release. It is > also too early to begin to think about 5.4 as there is still a couple > of things to clarify before. The most important ones being: Why have trunk then? 5.4 has a lot of things added to 5.3, merging them one-by-one to 5.3 would be just waste of time. > - What are the top new things we like to have in > - Define a clear release process (not going to go through a 5.3.0 or 6.0 again). > - Define the RMs, I do want a good, honest and respectful RMs. Go ahead, do that :) > The last point can wait as we are a couple of months away of defining > the first two. For example I have a couple of very important things to > add to the stack but I won't be able to describe them fully before > September (I'm in holidays now, remember that 5.3.3 is a couple of > weeks old...). It'd be alpha, you have enough time. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227