db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew McIntyre <mcintyr...@gmail.com>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Wed, 08 Jun 2005 17:38:55 GMT

On Jun 8, 2005, at 9:33 AM, David Van Couvering wrote:

> Thanks, Oystein, for the quick turnaround.  Your comments involve  
> some minor changes.  I can go ahead and do this and submit an  
> updated patch ASAP.  Someone let me know if you'd rather take what  
> I have now -- I am not clear on the constraints of the release  
> schedule.

There's not really a 'schedule,' so there aren't really any specific  
time constraints. :-)

My plan is to create a release whenever all the bugs targeted for the  
10.1 release are fixed. Currently, that includes Derby-243. Now that  
there are patches in review for all the issues targeted for 10.1, I'm  
guessing I'll be able to start putting binaries together for people  
to test by the end of the week, or early next week at the latest. So,  
if your patch is still pending a week from now, I'll probably suggest  
that we move it to 10.2, since it's not a showstopper. But  
considering how close it is to completion, that doesn't seem likely.

One thing to remember is that *anyone* can review patches. So, anyone  
with some free time should take a look at the remaining issues with  
patches pending:

http://issues.apache.org/jira/browse/DERBY-217
http://issues.apache.org/jira/browse/DERBY-319
http://issues.apache.org/jira/browse/DERBY-334
http://issues.apache.org/jira/browse/DERBY-337
http://issues.apache.org/jira/browse/DERBY-338
http://issues.apache.org/jira/browse/DERBY-339

The sooner patches are reviewed, the sooner they can be committed.

cheers,
andrew

Mime
View raw message