Return-Path: Delivered-To: apmail-excalibur-dev-archive@www.apache.org Received: (qmail 47072 invoked from network); 24 Aug 2005 13:41:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2005 13:41:25 -0000 Received: (qmail 64536 invoked by uid 500); 24 Aug 2005 13:40:52 -0000 Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org Received: (qmail 64483 invoked by uid 500); 24 Aug 2005 13:40:52 -0000 Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Excalibur Developers List" Reply-To: "Excalibur Developers List" Delivered-To: mailing list dev@excalibur.apache.org Received: (qmail 64450 invoked by uid 99); 24 Aug 2005 13:40:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2005 06:40:51 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.192.92.136] (HELO wrnxchg2.whiterocknetworks.com) (65.192.92.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2005 06:41:08 -0700 Received: from [127.0.0.1] ([192.168.28.48]) by wrnxchg2.whiterocknetworks.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Aug 2005 08:40:48 -0500 Message-ID: <430C78E0.9040503@badfw.org> Date: Wed, 24 Aug 2005 08:40:48 -0500 From: "Sasvata (Shash) Chatterjee" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Excalibur Developers List Subject: Re: One more change to be included into the release... References: <430C64F1.8090301@reverycodes.com> <430C748C.8000505@tanukisoftware.com> In-Reply-To: <430C748C.8000505@tanukisoftware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Aug 2005 13:40:48.0683 (UTC) FILETIME=[6FB667B0:01C5A8B1] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Leif, > > If we are going to do another RCn then I have a minor change of my own > for the > excalibur-instrument-mgr-impl jar. If not then it can wait until the > next release. > (A typo and removing a stack dump if the state file is corrupted or > can't be > accessed for any reason. It can happen if a previous JVM invocation > crashed > at just the wrong moment.) > You tell us. As the release-manager, here's my position: There's no sense doing a release, but leaving the community high and dry if they cannot use the release. So, tell us, if you can trudge along with using most of the new release, but use the previous fortress-meta. If you cannot do that, we'll do a RC4 and fix Vadim's (I think important, but non-blocker) issue, and you can fix the minor issue you mention here. But, here's the catch. I would not do the RC4 for another week, instead really *encouraging* all users to complete testing with RC3. Once we do RC4, the only things that will stop the release will be things broken between RC3 and RC4, but nothing else. Does that sound kosher? Shash --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org For additional commands, e-mail: dev-help@excalibur.apache.org