db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.
Date Tue, 25 Oct 2005 15:21:58 GMT
Thanks, Rick.  I'll test with this new patch.  Andrew, FYI, I'm working 
on running all the compatibility tests.  If these pass, I'm planning on 
committing Rick's patch.  Let me know if you have any further issues 
with his changes.

David

Rick Hillegas (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
> 
> Rick Hillegas updated DERBY-516:
> --------------------------------
> 
>     Attachment:     (was: bug516.diff)
> 
> 
>>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
> 
> 
>>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/
> 
> 

Mime
View raw message