Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 89658 invoked from network); 19 Jan 2005 22:49:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jan 2005 22:49:20 -0000 Received: (qmail 98813 invoked by uid 500); 19 Jan 2005 22:49:17 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 98781 invoked by uid 500); 19 Jan 2005 22:49:17 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 98768 invoked by uid 99); 19 Jan 2005 22:49:17 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of robertburrelldonkin@blueyonder.co.uk designates 195.188.213.5 as permitted sender) Received: from smtp-out2.blueyonder.co.uk (HELO smtp-out2.blueyonder.co.uk) (195.188.213.5) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 19 Jan 2005 14:49:15 -0800 Received: from [10.0.0.2] ([82.38.65.173]) by smtp-out2.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Wed, 19 Jan 2005 22:49:46 +0000 Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <54EEABB8-6A6C-11D9-A809-003065DC754C@blueyonder.co.uk> Content-Type: text/plain; charset=US-ASCII; format=flowed To: Jakarta Commons Developers List From: robert burrell donkin Subject: [logging][PROPOSAL] 1.0.5 release Date: Wed, 19 Jan 2005 22:49:09 +0000 X-Mailer: Apple Mail (2.619) X-OriginalArrivalTime: 19 Jan 2005 22:49:46.0153 (UTC) FILETIME=[2C55B990:01C4FE79] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N IMO the first step before any work can begin on any improvements is to release the current code (this contains an important enhancement improving memory release in the 1.0.x series of releases). therefore, i propose that we should start the release process for 1.0.5 by electing a release manager and formulating a release plan. i'm willing to act as release manager for this release. my vision would be that a release branch would be taken as soon as possible but with a long release candidate phase would follow to allow the release to be tested. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org