Return-Path: 
 <derby-dev-return-17246-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 20872 invoked from network); 19 Mar 2006 17:44:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Mar 2006 17:44:55 -0000
Received: (qmail 89411 invoked by uid 500); 19 Mar 2006 17:44:53 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 89328 invoked by uid 500); 19 Mar 2006 17:44:53 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 89204 invoked by uid 99); 19 Mar 2006 17:44:53 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Mar 2006 09:44:53 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [204.174.16.216] (HELO mailout6.parasun.com) (204.174.16.216)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Mar 2006 09:44:51 -0800
Received: from cpe-24-143-157-032.cable.alamedanet.net ([24.143.157.32]
 helo=[127.0.0.1])
	by mailout6.parasun.com with esmtp (Exim 4.54)
	id 1FL1x6-0003Kf-P9
	for derby-dev@db.apache.org; Sun, 19 Mar 2006 09:44:28 -0800
Message-ID: <441D9879.2080706@amberpoint.com>
Date: Sun, 19 Mar 2006 09:44:25 -0800
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Updated: (DERBY-1075) Combine the script and the test
 available for upgrade testing into a java test
References: <1812404810.1142470978813.JavaMail.jira@ajax>
In-Reply-To: <1812404810.1142470978813.JavaMail.jira@ajax>
Content-Type: text/plain; charset=UTF-8; format=flowed
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

Deepa Remesh (JIRA) wrote:
> It should be possible to add more tests using the jar locations for each old/new release combination to be tested. 
> 
> 2. The new master added 'UpgradeTester.out' is based on phaseTester.out with few diffs in the statements printed out.
> 
> To run upgrade tests using this class, use the command: 
> java UpgradeTester <location of old jars> <location of new jars> <old major version> <old minor version>
> e.g, java UpgradeTester C:\derby\10.1\lib C:\derby\trunk\lib 10 1

If we anticipate that we will eventually have several different upgrade
scenarios and combinations of releases that we desire to support, is it
worth spending a bit of time now coming up with naming conventions
for the master files so that it will be easy to tell them apart?

That is, should 'UpgradeTester.out' really be named something like
'UpgradeTester_10_1_10_2.out'?

thanks,

bryan