> (You have TO do something about that mail reader, the quote vertical / > comment horizontal thing is trippy but unreadable.)
I know. I'm thinking about actualy buying a better mail reader for my Palm, because the one that comes with it is quite fscked up. > > On Thu, Aug 24, 2000 at 09:34:08AM -0400, Timm Murray wrote: > > >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. > > Developing a kernel (and especially a mail fetching util) != developing a > Network. Ian keeps advocating in the release early/often thing, but then > we keep getting in situation where we have to change the protocol and make > things incompatible to people's annoyance. If we had a spec (like > posix) to follow thing would be very different around here. > > > But we can't do this with only two main developers. I suggest we put a > > 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. > > We do build and put out daily developer releases. It hasn't made > development one bit faster or higher quality. I hardly get any feedback at > all from people using them (except when the windows bat files get broken), > and I keep running into bugs that should have effected nodes for months > wondering, "Why didn't anybody tell me that this wasn't working?" I don't think thats surprising with only two people regularly working on the code. > > And as for "a major shoutout for new developers", that will, at best, > bring in a lot of people who think they can just start changing stuff > without understanding the system. Yeah, I know thats a problem. Thats why I say keep the code in a frozen state for a while after 0.3 so people can catch up. > > > _______________________________________________ > > Freenet-dev mailing list > > Freenet-dev at lists.sourceforge.net > > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > > > > -- > \oskar > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
