Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 63763 invoked from network); 4 May 2005 08:04:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 May 2005 08:04:01 -0000 Received: (qmail 82794 invoked by uid 500); 4 May 2005 08:04:05 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82639 invoked by uid 500); 4 May 2005 08:04:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 82581 invoked by uid 99); 4 May 2005 08:04:01 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from e34.co.us.ibm.com (HELO e34.co.us.ibm.com) (32.97.110.132) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 04 May 2005 01:04:01 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e34.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j4481xeE432794 for ; Wed, 4 May 2005 04:01:59 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j4481xxQ358196 for ; Wed, 4 May 2005 02:01:59 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j4481xBU023484 for ; Wed, 4 May 2005 02:01:59 -0600 Received: from [127.0.0.1] (sig-9-48-122-15.mts.ibm.com [9.48.122.15]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j4481qww022966 for ; Wed, 4 May 2005 02:01:58 -0600 Message-ID: <42788150.2010203@Sourcery.Org> Date: Wed, 04 May 2005 01:01:20 -0700 From: Satheesh Bandaram User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: Schedule for beta and release of 10.1 References: <426EA3DB.9050707@bellsouth.net> <426EA7D4.8080409@debrunners.com> <42781431.1050308@gmail.com> <42784236.70504@apache.org> In-Reply-To: <42784236.70504@apache.org> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N One month seems like a good amount time to figure out some of these, at least just to formulate a plan. I am eager to see Derby client get rigorous testing that precedes a full release and to get it to derby users. I am concerned about potential resource leakage, platform specific, multi-threading issues that may or may not be present. These issues are typically found and addressed during a full release process. I also think current dependence on JCC client driver in 10.0 hinders wider adaptability of Derby. You do raise some touch questions. :-) Like you suggested, we can work on getting a plan in place for these soon. Satheesh > I think aiming for a release in a month or so would be good. > > However, I do not want to rush out the first version of the client as > that will suddenly give us a legacy codebase. We have only just seen > this code and there are a couple of areas that we should consider: > > * which JREs will it run on > * do we need JSR-169 support > * what are the plans for SSL transport, including client auth > * what do we do with Referenceable > * what are our plans for connector support > * do we have the right properties > * do we change the commmand line processing for NetworkServer > > and probably a few more things as well. We don't need to resolve all > of these but at least figure out what the plan is. > > -- > Jeremy > > >