Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 60813 invoked from network); 5 Dec 2006 06:39:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Dec 2006 06:39:27 -0000 Received: (qmail 86870 invoked by uid 500); 5 Dec 2006 06:39:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 86660 invoked by uid 500); 5 Dec 2006 06:39:35 -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 86651 invoked by uid 99); 5 Dec 2006 06:39:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 22:39:35 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.19.6] (HELO sineb-mail-1.sun.com) (192.18.19.6) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 22:39:22 -0800 Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id kB56ctDN012256 for ; Tue, 5 Dec 2006 14:38:56 +0800 (SGT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0J9S00E01FQOZP00@mail-apac.sun.com> (original mail from Mayuresh.Nirhali@Sun.COM) for derby-dev@db.apache.org; Tue, 05 Dec 2006 14:38:55 +0800 (SGT) Received: from [129.158.227.167] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0J9S001X7FSVI96I@mail-apac.sun.com> for derby-dev@db.apache.org; Tue, 05 Dec 2006 14:38:55 +0800 (SGT) Date: Tue, 05 Dec 2006 12:08:35 +0530 From: Mayuresh Nirhali Subject: Re: upgrade testing In-reply-to: <457466CE.5020509@sbcglobal.net> Sender: Mayuresh.Nirhali@Sun.COM To: derby-dev@db.apache.org Reply-to: Mayuresh.Nirhali@Sun.COM Message-id: <457513EB.9090004@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <8061672.1164962123571.JavaMail.jira@brutus> <4570BF8C.80901@amberpoint.com> <4573F094.8000208@Sun.COM> <45743E19.9030805@amberpoint.com> <457440B0.8070704@apache.org> <457466CE.5020509@sbcglobal.net> User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20060120 X-Virus-Checked: Checked by ClamAV on apache.org I see. This explains why the other upgradeCases were not removed from the framework. So, no clean up is required. then, I will file a JIRA to track supporting upgrade from any release for the current framework. It will be worth considering converting this test to JUnit as a part of this effort! mayuresh Mike Matrigali wrote: > I believe that the goal is to be able to upgrade from any release. > I think what you are seeing is that tests haven't caught up with > the upgrade support we want to provide. I believe we should be > able to hard upgrade a 10.1 db straight to a 10.3 db. > > Daniel John Debrunner wrote: > >> Bryan Pendleton wrote: >> >>> Mayuresh Nirhali wrote: >>> >>>> I believe, the upgrade model we follow implies that the upgrade is >>>> possible *Only* from the previous major.minor release. So, the >>>> upgrade test for 10.3 will only test any possible upgrades from 10.2. >>> >>> >>> >>> That makes sense. Thanks for clarifying. >> >> >> >> Upgrade is possible from any previous release. The origins of the >> upgrade test was that any release could be plugged in as the base (to >> be upgraded release), even the same version. >> >> >> Dan. >> >> >> >