Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 54298 invoked from network); 21 Jul 2005 09:18:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Jul 2005 09:18:19 -0000 Received: (qmail 19475 invoked by uid 500); 21 Jul 2005 09:18:19 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 19462 invoked by uid 99); 21 Jul 2005 09:18:19 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2005 02:18:19 -0700 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=SPF_HELO_FAIL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.110.133] (HELO e35.co.us.ibm.com) (32.97.110.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2005 02:18:13 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j6L9IBZv150456 for ; Thu, 21 Jul 2005 05:18:15 -0400 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j6L9IBvk405556 for ; Thu, 21 Jul 2005 03:18:11 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j6L9IBVW012268 for ; Thu, 21 Jul 2005 03:18:11 -0600 Received: from [127.0.0.1] (sig-9-48-124-196.mts.ibm.com [9.48.124.196]) by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j6L9I6mS012187 for ; Thu, 21 Jul 2005 03:18:10 -0600 Message-ID: <42DF684C.3040304@debrunners.com> Date: Thu, 21 Jul 2005 02:18:04 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Re: JDO API compability with JDK 1.3 X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > From: Michael Bouschen > I have a question what kind of JDK 1.3 compatibility do we want to > support? I see that JDO plans to support JDK 1.3 from the wiki, but I was wondering why? Given the end of service dates for the various 1.3 VMs I was thinking that Derby 10.1 could be the last release to support 1.3. However if there's a good reason, and JDO would be one, Derby would not remove 1.3 support, but I am curious what lead JDO to this decision. Dan.