Except for those manually updating like me or those running without the
wrapper. Interesting idea though. I wonder how many manually update? From
my casual observations 90% of nodes are updated within 2 hours of Toad
pushing a new version into the network.
On Nov 4, 2010 1:29 PM, "Gerard Krol" <gerard at gerardkrol.nl> wrote:
> On Sat, Oct 30, 2010 at 5:59 PM, Matthew Toseland
> <toad at amphibian.dyndns.org> wrote:
>> On Friday 29 October 2010 17:24:30 Robert Hailey wrote:
>>> It's too bad that there is not a way to experiment on the whole
>>> network without negatively effecting it; e.g. it would be *very* bad
>>> if a routing change prevented update-over-freenet. I guess we could
>>> run two parallell networks, but would require reduplicating much code.
>>
>> Update Over Mandatory means auto-update will work in *almost* all cases
unless we *really* mess things up in e.g. the transport layer or
announcement.
>
> I suggest we advertise a specific (testing) version for a certain time
slot:
> version 3000, in effect from Thursday November 11 2010 12:00 UTC to
> Thursday November 11 2010 13:00 UTC
> If you start advertising it early (on the 7th for example) then all
> nodes will have had plenty of time to download the testing version.
> After an hour of testing (of after an hour of fatal Freenet outage),
> every node will revert to the stable version and everything will be
> back to normal.
>
> We already had a small discussion about this over IRC. A possible
> problem that came up was that it would be bad if the clock on some of
> the nodes would be out of sync. I suppose it wouldn't really matter if
> it is only a small fraction of the nodes.
>
> - Gerard
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20101104/d2ca0b01/attachment.html>
