db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Clary" <jcl...@actuate.com>
Subject RE: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database
Date Wed, 28 Mar 2007 18:04:28 GMT
Unfortunately, as a new Derby contributor, I am still working the kinks out of my building
and testing.  I haven't been able to get a clean baseline test for derbyall, and I haven't
tried suites.All.  I'll get to that eventually, but maybe in the meantime a submitter will
see in JIRA that you ran the tests successfully.

Thanks for the tips.  I'm working toward lining my ducks all up in a row.


-----Original Message-----
From: John.Embretsen@Sun.COM [mailto:John.Embretsen@Sun.COM] 
Sent: Wednesday, March 28, 2007 10:10 AM
To: derby-dev@db.apache.org
Subject: Re: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using
EmbeddedDriver on non-existent database

Jeffrey Clary wrote:
> Thanks for the review.  This is the first time I have contributed any code (one line
;-) to Derby.  At this point will the fix be picked up by a submitter or is there something
else I need to do to make sure it gets into the next release?

I see that you have set the "Patch available" flag, so in theory everything 
should be ready for a committer to review and (hopefully) commit the patch. You 
should state the results of your test runs (derbyall, suites.All), though.

Further advice is described here:

http://wiki.apache.org/db-derby/PatchAdvice

-- 
John


Mime
View raw message