db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Features - Quick or correct??
Date Fri, 10 Dec 2004 19:22:22 GMT
Hash: SHA1

RPost wrote:

>>Jack Klebanoff wrote:
>>I wanted to make an initial implementation that is simple, handles both
>>INTERSECT and EXCEPT, and that fits into the current Derby
>>implementation fairly easily. If the performance of INTERSECT or EXCEPT
>>proves to be important then we should revisit this.
> I certainly agree with this approach. The first priority is to get
> that works
> as easily and simply as possible.

I'm not completely convinced this is the correct approach. While it is
good to have the functionality (and maybe more importantly the tests)
quickly, first impressions count. So if we (the Derby community) produce
correct but slow features, it will be hard to shake that image.

Contributors & committers should be encouraged to discuss design ideas
with the list early rather than once they have coded them up.

It's also hard for me to tell with various contributions if the
contributor thinks the feature is complete, or it's an incremental step
to the fully completed feature. I think the incremental step is a great
way to go, but only if it's identified as that, and the future steps are
listed so the contributor or someone else can address them. Then it's
also easy to discuss which of those steps are essential before a feature
is considered ready for production release.

Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


View raw message