I think you are quite right that this is most likely too long to wait
for the next release. I think what Rick is saying is his personal itch
is JDBC4, that's the release he wants to manage, and he's not up for
managing two releases in a row.
I am hoping (and I am sorry to say I am not the one to do this with a
new baby) that someone can volunteer to manage an earlier release so we
can get some of this great new functionality (other than JDBC4) out to
our users.
Helpful hint to anyone thinking of doing this: it is pretty darn easy to
build a binary of Derby that does not include JDBC4 - just don't compile
it with the JDK 1.6 compiler... So hopefully we do not have to yank out
all the JDBC4 work to do a release prior to the GA of the JDBC4
specification.
David
Kathey Marsden wrote:
Rick Hillegas wrote:
AHowever, because the JDBC4 schedule moved back, I must post my
release later, most likely in October.
My big issue with this is that we seem to be totally deviating from a
major tenant of of open source development.
/Release early. Release often. And listen to your customers.
/
http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html
How will we in the Derby development community reign in quality and
compatibility issues especially with client and get the needed user
feedback with such a long release cycle?
Kathey
