Return-Path: 
 <commons-dev-return-14009-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 95215 invoked from network); 15 Aug 2002 16:42:46 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 15 Aug 2002 16:42:46 -0000
Received: (qmail 7369 invoked by uid 97); 15 Aug 2002 16:43:06 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org
Received: (qmail 7319 invoked by uid 97); 15 Aug 2002 16:43:05 -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-Subscribe: <mailto:commons-dev-subscribe@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 7280 invoked by uid 98); 15 Aug 2002 16:43:04 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
Message-ID: <3D5BD9F9.1080306@apache.org>
Date: Thu, 15 Aug 2002 18:42:33 +0200
From: Remy Maucherat <remm@apache.org>
Organization: ASF
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.1b) Gecko/20020721
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [VOTE][DBCP] 1.0 Release Plan
References: <3D5BD893.9060504@mail.more.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Glenn Nielsen wrote:
> Craig and I came to the conclusion that a formal release plan and
> vote had not taken place for a DBCP 1.0 release.  Craig said he
> no longer had time to continue with this.  Tomcat 4.1.x is getting
> close to a final release and needs to include a released version
> of DBCP.
> 
> DBCP 1.0 Release Plan
> ---------------------
> 
> Build DBCP w/o jdbcb2pool and w/o dependency on commons-lang.
> Modify build.xml to support building either DBCP or jdbc2pool.
> 
> Build both JDK1.3 and JDK1.4 versions of DBCP.  Sign the releases.
> 
> branch CVS for jakarta-commons/dbcp 1.0 release.
> 
> I can act as release manager.
> 
> <Ballot>
> +1 [ ] Do the release, I can help
> +0 [ ] Do the release
> -0 [ ] Not happy with the release but I won't veto it
> -1 [ ] Don't do the release for the following reasons
> </Ballot>

+0. (I want it, and I need it; Tomcat users need DBCP badly too)

(I have a non binding vote, so sorry, I can't +1)

I'm not sure branching is needed, since the component is quite small. 
Many commons components are doing fine without branching.

Remy


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