Kathey Marsden <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> I plan to do this as soon as the fix for DERBY-3347 has been merged to >> the 10.4 branch, and then call for a vote on the new RC. >> >> > It would be great also to see the alternate fix for DERBY-2892 go in > and then it will eliminate the necessity for the release note and > incompatibilities in the 10.4 release.
Thanks for bringing this up. These are the chekins that have been made to 10.4 after 10.4.1.1 was spun: ------------------------------------------------------------------------ r645438 | kristwaa | 2008-04-07 12:03:01 +0200 (Mon, 07 Apr 2008) | 4 lines DERBY-3571: LOB locators are not released if the LOB columns are not accessed by the client. Merge from trunk revision 643819 (derby-3571-2a-simple_release.diff). The patch added the client side LOB state tracking, used to release LOB locators in a timely manner. ------------------------------------------------------------------------ r645706 | mamta | 2008-04-07 23:45:48 +0200 (Mon, 07 Apr 2008) | 10 lines migrating revision 645665 from trunk into 10.4 codeline (DERBY-3320). The commit comments were as follows Fix for the test that was added for DERBY-3320. The test was using DriverManager.getConnection but DriverManager is not available in JSR 169 environment. This caused the test to fail when run in JSR 169 environment. I have fixed the test to use testUtil.getConnection which is smart enough to use DriverManager or DataSource depending on what VM the test is getting run in. ------------------------------------------------------------------------ > Kristian said: > > Committed to trunk with revsion 646255. > I plan to backport the fix to 10.4 when the last patch has been > committed, and also investigate the possibility of backporting to > 10.3. > [ Show ยป <https://issues.apache.org/jira/browse/DERBY-2892> ] > Kristian Waagan > <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kristwaa> > - > 09/Apr/08 03:21 AM 'derby-2892-1b-alternative_fix_partial.diff' is > slightly changed from 1a; reordered keywords (abstract public -> > public abstract) and removed an added blank line. Committed to trunk > with revsion 646255. I plan to backport the fix to 10.4 when the last > patch has been committed, and also investigate the possibility of > backporting to 10.3. > > > I'm not sure of the timeframe. I'd be happy to help in anyway I can. I believe Kristian is at ApacheCon Europe, but I'm willing to merge these fixes to 10.4. What about the last patch 'derby-2892-2a-alternative_fix_cleanup.diff'? Should that be committed to trunk and merged as well, or is that less urgent? -- dt
