db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.
Date Mon, 07 Feb 2011 21:59:58 GMT

     [ https://issues.apache.org/jira/browse/DERBY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-516.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.2.1.6

I've promoted the former subtask DERBY-1048 to an improvement, and am closing this issue again.

> Need to incorporate client backward/forward  compatibility testing into testing procedures.
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-516
>                 URL: https://issues.apache.org/jira/browse/DERBY-516
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.1.1.0
>            Reporter: Kathey Marsden
>             Fix For: 10.2.1.6
>
>         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/<framework>/ver<version>  
> functionTests/master/<framework>/
> functionTests/master/

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message