Stricter upgrading sounds good to me if it helps bring the network out
of this hole... but I do think that, while the technically minded among
us play with the latest code, some of us reside on a separate network
so we can enjoy freenet for what it really is.

For those wanting to give this a try, see http://mids.student.utwente.nl/~mids/freenet/

I'll be inserting YoYo on both networks to make things easier for those
that make the transition.

--Reskill

On Sun, 05 Oct 2003 12:15:01 -0700 Ian Clarke <[EMAIL PROTECTED]> wrote:
>Ok, lets put this to bed.   My intention was not to appear dismissive
>of 
>people's concerns, but it is easy to get frustrated by non-specific
>>
>criticism when I, and several others, have spent many hours trying
>to 
>investigate these problems.  The kind of careful detective work
>required 
>to identify and solve these problems doesn't respond well to pressure
>- 
>but it does respond well to people who take the time to understand
>what 
>is going on and do what they can to help.  A number of people have
>taken 
>the time to look at the NGR code, which isn't really *that* complicated,

> 
>and asked questions about things that didn't make sense.  This is
>very 
>useful indeed.
>
>If there is a clearly defined previous build of Freenet that works
>well, 
>then we should consider having a more clearly defined distinction
>>
>between production and stable.
>
>My main concern with having separate networks is that it becomes
>>
>virtually impossible to determine whether the development build is
>>
>performing better or worse than the stable builds because they will
>be 
>separate networks with different usage patterns.  Freenet is much
>more 
>difficult to debug and analyze than most software because its 
>effectiveness can only really seen in the interaction  of many Freenet
>>
>nodes, not just the behavior of one - although NGR helps in this
>regard.
>
>There is, however, the advantage that we can get away with a much
>>
>stricter upgrade regime in the unstable builds, I would almost advocate
>>
>making the lastGoodBuild the current build -3 by default in a dedicated
>>
>development network.
>
>Another thing to consider is how we handle the transition from the
>>
>current architecture.
>
>Thoughts?
>
>Ian.
>
>_______________________________________________
>Devl mailing list
>[EMAIL PROTECTED]
>http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to