db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: embedded derby -- does it leak
Date Wed, 15 Feb 2006 21:52:56 GMT
I can't speak officially for Sun, but I do know that it has always been 
the intent of the Sun Derby development team for *all* 
patches/bugfixes/changes made for customers of Java DB to be made in the 
Derby code base, not on some separate forked version of the code.

David

derby@segel.com wrote:
> 
>>-----Original Message-----
>>From: David W. Van Couvering [mailto:David.Vancouvering@Sun.COM]
>>Sent: Wednesday, February 15, 2006 10:54 AM
>>To: Derby Discussion
>>Subject: Re: embedded derby -- does it leak
>>
>>We do a *lot* of testing, including long-running tests and large
>>database size tests.  We're trying to add more and more tests,
>>robustness and compatibility are key goals for many of us on this team.
>>
>>If you really need a production-level support, you should probably go
>>through Sun (Java DB) or IBM (Cloudscape).
>>
>>David
>>
> 
> [mjs] 
> This then begs the question....
> 
> Suppose a *supported* customer finds a bug. Does that mean that either SUN
> or IBM which offers support, will fix said bug? Will they then release it
> back to the general community, or do they intend to maintain their own
> patched distribution chain?
> 
> I know I've asked this question a couple of times, yet no one from either
> Sun or IBM are willing to respond.
>  
> [SNIP]
> 
> 

Mime
View raw message