Return-Path: 
 <commons-dev-return-83520-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 30461 invoked from network); 23 Jan 2006 01:40:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 23 Jan 2006 01:40:24 -0000
Received: (qmail 24521 invoked by uid 500); 23 Jan 2006 01:40:21 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 24497 invoked by uid 500); 23 Jan 2006 01:40:21 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 24486 invoked by uid 99); 23 Jan 2006 01:40:21 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2006 17:40:21 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.162.207 as permitted sender)
Received: from [64.233.162.207] (HELO zproxy.gmail.com) (64.233.162.207)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2006 17:40:20 -0800
Received: by zproxy.gmail.com with SMTP id 8so834641nzo
        for <commons-dev@jakarta.apache.org>;
 Sun, 22 Jan 2006 17:40:00 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Rr75NBNaFhJZwzDEvhtK3zYnti2fMuqcBZIIPCYUE/w/qDvIQB06P2T6m7uJHbAnfnrLDQWjf6LjZQgKPaK6789NuOa/BJA6kYh0lz93mVOa22xxMuopCEU4rcojfDCi1O5EUyFw55a8CnyaakLpom41WPOGUV0dEEkRZMYKB0w=
Received: by 10.37.2.80 with SMTP id e80mr3509500nzi;
        Sun, 22 Jan 2006 17:40:00 -0800 (PST)
Received: by 10.36.24.16 with HTTP; Sun, 22 Jan 2006 17:40:00 -0800 (PST)
Message-ID: <ce1f2ea80601221740x180f590dr6a946cd75203534f@mail.gmail.com>
Date: Sun, 22 Jan 2006 20:40:00 -0500
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [logging] please check release candidate 1
In-Reply-To: <1137978778.7814.31.camel@knossos.elmet>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1137978778.7814.31.camel@knossos.elmet>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 1/22/06, robert burrell donkin <rdonkin@apache.org> wrote:
> i've uploaded RC1 to http://people.apache.org/~rdonkin/commons-logging/.
> please check and test the release candidate and report any mistakes or
> problems.
>
> you'll probably notice that the jars are numbered 1.1 (not 1.1RC1 as is
> more usual). i'd like to use a variation of the httpd/struts/tomcat
> release approval process. i'll outline how this would work tomorrow.
>
<snip/>

Folks -

Sincere apologies if this seems to be in the way of anyone doing the
real work. There are jars out there marked 1.1, and I'm not
comfortable with this. I'm aware of the httpd/struts/tomcat process,
but we need to collectively decide before any components start
deviating from (what I understand is) Commons policy.

I'm all for JCL 1.1, but IMO, the above approach should have been
discussed before posting these files.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org