Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 14763 invoked from network); 1 May 2007 19:07:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 May 2007 19:07:31 -0000 Received: (qmail 46563 invoked by uid 500); 1 May 2007 19:07:34 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 46353 invoked by uid 500); 1 May 2007 19:07:33 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 46333 invoked by uid 99); 1 May 2007 19:07:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2007 12:07:33 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [209.133.199.10] (HELO jimsys.jagunet.com) (209.133.199.10) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2007 12:07:26 -0700 Received: from [127.0.0.1] (localhost [127.0.0.1]) by jimsys.jagunet.com (Postfix) with ESMTP id DED316D96C0; Tue, 1 May 2007 15:07:05 -0400 (EDT) In-Reply-To: References: <200704271649.52237.daniel.kulp@iona.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: cxf-dev@incubator.apache.org Content-Transfer-Encoding: 7bit From: Jim Jagielski Subject: Re: [VOTE] approve release of CXF 2.0-incubator-RC Date: Tue, 1 May 2007 15:07:05 -0400 To: general@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org On May 1, 2007, at 11:53 AM, Leo Simons wrote: > > There's a STATUS file which says its from 2004 and is definitely > not updated (Dan tells me Jim said this was ok). > Not enough to hold it off, no, but either the file should be updated or removed the next go around.