On Fri, Aug 26, 2011 at 11:50 AM, Matthew Toseland <toad at amphibian.dyndns.org> wrote: > Freenet 0.7.5 build 1401 is now available. Please upgrade, it will be > mandatory at midnight. This build turns off New Load Management, for the time > being. If performance continues to be poor we will know the problem is > elsewhere (it is possible that it is a problem with the asyncGet changes, > although I don't see how). There are also fixes related to dropping peers due > to the one IP per connection setting. You should not normally enable this > setting on darknet (core settings); it can cause your friends to be lost. > > Thanks, and sorry for all the problems lately.
Was it really necessary to have the update be mandatory on such short notice? I'm not trying to be sarcastic, this is a serious question and I'm curious about your opinion. It seems to me that you get most of the impact thanks to the auto-updates, which most of the network uses. Some of us, however, do not. I can't use the auto-update without it regularly interfering with the network size graphs I produce. (Yes, the scripts that run it are brittle and sensitive to things like that. Yes, I'd like to throw them out and write something better, but motivation to actually do that has yet to strike.) So I have to manually perform updates at times when they aren't running, and I missed the window on that one. The result is wonky network size info that I'm pretty sure is entirely an artifact of that, and has no relationship to what the recent performance issues have done to network size, which would have been an interesting question. Anyway, a little more warning would have been nice, but obviously the health of the network comes first. Is there a policy on what the requirements are for a build to be made mandatory at all? And what the warning period should be? If not, it seems like something we should have. Evan Daniel
