db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: Proposal for 10.2 release schedule
Date Thu, 22 Jun 2006 22:58:37 GMT
David Van Couvering wrote:
> In order for this to work, we need Java DB to be based on an official,
> "GA-ready" release of Derby to be what Sun redistributes in Mustang.
> Otherwise databases created in Mustang will be "locked in" to Java DB.
> The problem is that it can't *actually* be GA until after JCP approves
> JSR 221, JDBC 4.0, which will happen in tandem with the GA release of
> the JDK, around 5 weeks after the JDK team needs their final integration
> bits from all the pieces going into it.

in other words, we have a classic catch-22. :-)

> I think what Rick is asking for is a release that is voted as
> "GA-ready", has the GA-bit turned on, but because of JCP rules is not
> actually *made* generally available until JSR 220 becomes final.  Since
> we all need to vet this release and approve it, it would be available to
> the Derby community, but not *generally* available by distributing it on
> all the Apache mirrors.

It would still be easily available. And once downloaded, and probably
redistributed further, downstream users would have no idea that they
aren't working with an official Apache release.

What is the specific legal verbiage we're working with here?


> I know this seems like a fine hair to split, but it's the only way we
> can be successful without Sun having to do a non-upgradable fork of
> Derby, which I don't think any of us want.
> I hope this helps to clear things up, even if it doesn't make things
> simpler :)
> David

View raw message