>Since >there is no deadline it is >likely best to do it right >rather than release buggy >software at a fast and >furious rate by taking the >popular shotgun approach to >QA.
Actually, we might look into getting a faster development time useing theories learned from the Linux kernel development and outlined in 'The Cathedral and the Bazaar.' This does not meen poor-quality code by any means; in fact it meens better code because there are more people grocking over it. But we can't do this with only two main developers. I suggest we put a major call-out for new developers as soon as 0.3 reaches a stable state and certain docs are updated. Give them time to get used to the existing code. From then on, release new developer releases (numbered 0.3.1, 0.3.2, etc.) until you get 0.4 in a stable state. Make these developer relases come out as fast as possible--once a day, if you can. This should lead to much faster devel time with higher quality code. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
