Hi guys, The "release early, release often mantra" is just as good and just as bad as "when it's ready and clean". It's good that some of us push one way, some push the other.
Just a few more words about not rushing: It's sad that we have to tell several people to use SVN. But I'm convinced that there are also many people happily using released versions. Most importantly, using SVN is not as difficult as Sam implied: compiling liquidsoap is difficult. Between compiling the tarball and SVN, the only difference is literally svn co and bootstrap. What is difficult for somebody learning liquidsoap is to find bugs! So we should not "release whatever we have": if we know of bugs or odd behaviors in our code, we should fix them! It's not very hype to cite Larry Wall anymore, but he said that programming is (among other things) about hubris. You should want to be proud of your code, and I know a few files that don't deserve it. Anyway, I think we're in agreement that we'll start with a second beta release. Also, Sam proposed that we do an intensive session on cleaning up I/O code, and Romain actually started doing changes there. This is all great, and I'm happy to release as soon as we reach a statu quo on I/O. I'll participate in any discussion on that topic, and I'll join coding as soon as possible -- but that may not be before the second half of this month... Cheers, -- David ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Savonet-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-devl
