You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/09/07 23:27:26 UTC
[jira] Updated: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Rick Hillegas updated DERBY-1746:
---------------------------------
Urgency: Normal (was: Urgent)
Degrading the urgency of this bug. Both 10.1 versions are reasonable starting points for upgrade and I would not let this issue block the release.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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