+1, I agree it's just too tight for 10.3. I'd like your response to my proposal for the experimental directory; right now I'm moving forward with it (for checkin to the trunk *after* we branch for 10.3).
The one thing I want to see is making our daily builds available for download so that people can play with our stuff (or is that already available and I don't know about it?) I have some other ideas on making it easier for users to experiment with new functionality that hasn't found itself in a release yet, but I'll wait until after the 10.3 crunch to discuss it. David On 6/13/07, Bernt M. Johnsen <[EMAIL PROTECTED]> wrote:
I have observed the mailings and comments wrt. checking in the JNLP stuff (DERBY-2469) for 10.3, possibly as an "experimental module". I oppose that for the following reasons: 1) It's not tested enough. 2) We have no procedures for experimental modules. We should not device such a thing so close to the 10.3 release. But it might be a good idea to discuss the need for experimental modules *after* 10.3 and in good time *before* 10.4. 3) Since Derby is open source, anyone who whish to experiment with this, may check out the trunk and apply the patch (that's the beauty of open source, no need for binary experimentals). -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway
