On Oct 21, 2005, at 9:18 PM, Daniel John Debrunner wrote:
<snip lots of good examples>
+1! To paraphrase a recent movie catch phrase: "Show me the code!" It's a lot easier to talk about something concrete than something abstract and vague. And, as long as anyone contributes something real that has definite value to the project, who is going to turn it down? You'd have to be crazy! :-) I admit this is a very different approach than the usual closed source way of spec-it-out and then implement the spec approach. It's more like implement-your-proposal and let the community comment. This is why I voted -0 to the recent Junit vote. It's great that members of the community are interested in developing Junit tests for Derby. But it doesn't mean much to say that we require Junit for testing when there are no Junit tests for other contributors to run, validate, and enhance. Speaking of which: Rick - I promise I'll get around to reviewing your contribution of new Junit compatibility tests w/r/t DERBY-516 as soon as I can (early next week?). I guess it's also important to understand that everyone has a limited amount of time and that individuals get things done according to how strong their itch for that particular subject happens to be. andrew |