Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 99465 invoked from network); 7 Nov 2005 20:18:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Nov 2005 20:18:52 -0000 Received: (qmail 15475 invoked by uid 500); 7 Nov 2005 20:18:52 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 15451 invoked by uid 500); 7 Nov 2005 20:18:51 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 15442 invoked by uid 99); 7 Nov 2005 20:18:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Nov 2005 12:18:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.34] (HELO brmea-mail-3.sun.com) (192.18.98.34) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Nov 2005 12:18:45 -0800 Received: from phys-d3-ha21sca-2 ([129.145.155.165]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id jA7KIP3H027146 for ; Mon, 7 Nov 2005 13:18:30 -0700 (MST) Received: from conversion-daemon.ha21sca-mail1.sfbay.sun.com by ha21sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IPL00101PLQSI@ha21sca-mail1.sfbay.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Mon, 07 Nov 2005 12:18:48 -0800 (PST) Received: from [129.150.27.79] (vpn-129-150-27-79.SFBay.Sun.COM [129.150.27.79]) by ha21sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IPL00JV3PRC5X@ha21sca-mail1.sfbay.sun.com> for derby-dev@db.apache.org; Mon, 07 Nov 2005 12:18:48 -0800 (PST) Date: Mon, 07 Nov 2005 12:18:33 -0800 From: Rick Hillegas Subject: Re: Question about client compatibility testing and DERBY-516 (paging Rick #:)) In-reply-to: <436FA94C.9040507@sbcglobal.net> To: derby-dev@db.apache.org Message-id: <436FB699.7080004@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) References: <436F9BD7.7070408@sbcglobal.net> <436FA4F0.3010607@sun.com> <436FA94C.9040507@sbcglobal.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Kathey, That sounds like a useful combination: 10.1.1.0 client against the mainline server, both running on the 1.4 vm. You see a lot of support cases and are in a good position to describe the main execution path. I don't have a lot of perspective here. Cheers, -Rick Kathey Marsden wrote: >Rick Hillegas wrote: > > > >>Hi Kathey, >> >>My initial ramblings on this topic start out at the end of August in >>the email thread "client/server compatibility testing". There I >>worried that over time, the compatibility tests could grow large >>(taking maybe 5 minutes per combination) and so, if run for all the >>combinations, would make derbyall take too long. That's why we're only >>runing one combination as part of derbyall. That combination doesn't >>really track a compatibility issue, it just tracks regressions which >>might creep into the test as other code changes. >> >>I'm certainly in favor of running all the combinations on a nightly or >>weekly basis and as a sanity check when cutting release candidates. >> >> >> >It seems that it would be worthwhile to enable the test with the 10.1 >jars (original client release) as it would make a clear statement of >the minimum client/server jar combinations that are expected work, would >probably catch most things that might break over time, and hopefully >would not add too much time. > >What do you think? > >Kathey > > > > > > >