I see your point, but we are working in a collaborative
environment, and the node ops time is important too.
Maybe less that the core developers one, but still important.
This is the "Stable" release, and 5087
is crap^h^h^h^h er... unworkable.
... the user too deserve some attention when
Umm, it ran out of memory. You can either wait for 5088 or increase the
-Xmx setting.
On Tue, Jul 27, 2004 at 05:32:41PM -0700, miguel wrote:
> For the first time since I started Freenet some 10 months ago it has failed!
> Build 5085 was fine. 5086... trash. Downhill. It would not find even YoYo
Oh, come now. Does not anyone remember that a version number below 1.00
or a variation there of means "developmental."
As long as any software is developmental it means failures of a new
version is almost certain. Even multi-billion companies can seldom
produce software that runs on every mach
For the first time since I started Freenet some 10 months ago it has failed!
Build 5085 was fine. 5086... trash. Downhill. It would not find even YoYo, plus,
it would just disconnect after 4 or 5 hours. This is a first for me since I usually
run
Freenet for days without a restart.
Enter 5087.