How about we do something like the Linux kernel, just on a smaller scale, and fork the code on Monday when we release. That way, we keep a 0.2x tree for making fixes to release should any big bugs occur, but sticking to the 1.2 protocol and not adding any real new features, while we move to a 1.3 protocol right away in the main CVS so that we can start experimenting with the new features.
On Thu, 27 Apr 2000, Brandon wrote: > > Hi All, > > > > What are people's opinions as to the proposed 0.2 release next Monday - > > GO! or NO GO!? > > I think we might as well. I don't think there's anything radically new and > having everyone upgrade would get rid of some lagging old nodes that are > slowing things down. > > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
