Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 73961 invoked from network); 15 Aug 2002 10:50:47 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Aug 2002 10:50:47 -0000 Received: (qmail 12327 invoked by uid 97); 15 Aug 2002 10:51:10 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12311 invoked by uid 97); 15 Aug 2002 10:51:09 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12299 invoked by uid 98); 15 Aug 2002 10:51:09 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D5B877B.3020709@users.sourceforge.net> Date: Thu, 15 Aug 2002 12:50:35 +0200 From: Alexis Agahi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en,fr MIME-Version: 1.0 To: Avalon-Phoenix Developers List Subject: Re: Features for next Phoenix Beta. References: <3D59F3E3.1070802@yahoo.com> <3D5A3F76.3020305@apache.org> <200208142136.38614.peter@apache.org> <200208141009.17132.proyal@apache.org> <3D5A7C7F.9090508@apache.org> <3D5B586B.70304@yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Paul Hammant wrote: > Stephen, Both Peters, > > *Please* could we cap the features now for 4.0. It is *really* > important for my company to have a non-beta release in weeks rather than > months. Mauro Talevi hints at the same need. > > All the exiting stuff you are pushing towards will be great for the 4.1 I 100% agree with Paul. And also it should be great to have shorter release cycle especilly for Phoenix ;) Would it be possible to branch the current cvs tree to have a stabilisation branch for Phoenix 4.0 and a dev path for 4.1 with features addon. -- To unsubscribe, e-mail: For additional commands, e-mail: