Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 1089 invoked from network); 10 Dec 2005 01:46:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Dec 2005 01:46:32 -0000 Received: (qmail 4252 invoked by uid 500); 10 Dec 2005 01:46:31 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 4232 invoked by uid 500); 10 Dec 2005 01:46:31 -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 4223 invoked by uid 99); 10 Dec 2005 01:46:31 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2005 17:46:31 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 6D6D718C for ; Sat, 10 Dec 2005 02:46:10 +0100 (CET) Message-ID: <1834563603.1134179170446.JavaMail.jira@ajax.apache.org> Date: Sat, 10 Dec 2005 02:46:10 +0100 (CET) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Reopened: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures. In-Reply-To: <206492626.1124374811599.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 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 [ http://issues.apache.org/jira/browse/DERBY-516?page=all ] Kathey Marsden reopened DERBY-516: ---------------------------------- I am reopening this bug as Rick plans to bring this test into derbyall by checking in the 10.1.1.0 release so that compatiblity testing with the first official derby release can be included in derbyall. Thanks Rick ! > Need to incorporate client backward/forward compatibility testing into testing procedures. > ------------------------------------------------------------------------------------------- > > Key: DERBY-516 > URL: http://issues.apache.org/jira/browse/DERBY-516 > Project: Derby > Type: Test > Components: Test > Versions: 10.1.1.0 > Reporter: Kathey Marsden > Assignee: Rick Hillegas > Attachments: bug516.diff > > Need to incorporate client backward/forward compatibility testing into testing procedures. > New versions of the Derby network server should work with old versions of the network client. New versions of the Derby network client should work with old versions of the server. Currently that means that the 10.1 client should be tested on the trunk. The 10.2 client definitely needs to be tested with the 10.1 server before release, but it would be good to start testing snapshots of 10.2 client on the 10.1 branch earlier. > > Note: > Bug fixes may mean that the canons differ for different versions. > The test harness I think is set up to allow different masters for different versions. It at least has that functionality for the DerbyNet framework > and it could be expanded to cover DerbyNetClient. The way it works is that > the harness checks for a masters in the following order: > functionTests/master//ver > functionTests/master// > functionTests/master/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira