[ http://issues.apache.org/jira/browse/DERBY-1569?page=all ]
Rick Hillegas updated DERBY-1569:
---------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> analyze 10.1 tests with 10.2 derby to determine which Jira fixes in 10.2 may
> have existing application impact
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1569
> URL: http://issues.apache.org/jira/browse/DERBY-1569
> Project: Derby
> Issue Type: Task
> Components: Test
> Reporter: Kathey Marsden
> Fix For: 10.2.3.0
>
>
> Running the 10.1 tests against 10.2 Derby is like running an existing
> applcation against Derby. There are many diffs and most intentional changes,
> but looking through the diffs can help highlight issues that may impact
> existing applications.
> Results of running 10.1 tests with 10.2.0.3 alpha are posted at:
> http://people.apache.org/~kmarsden/10_1_tests_10_2_derby/
> 10.2.0.3 is a bit old now. It might be good to do a new run but after the
> decimal getColumnDisplayWidth changes the new set of diffs might be harder to
> read.
> It would be good to go through the results, do an analysis, find any
> potential regressions or identify issues with significant impatct to existing
> applications. Then mark the Jira checkboxes and make an appropriate release
> note if needed. Not every intentional change or failure needs to be
> recorded, just ones applications are likely to hit and have an issue with.
> If this is not addressed by 10.2 release the issue can be closed.
> RegressionSearchAndDestroy hint.
--
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
