hi,
having had this discussion a lot the last month, I want to raise it again
from the dead.
I'm quite as unhappy as Matthias "don't upgrade...".
The releases of the stable branch where not as stable as I would expect from
a stable build (e.g. mutt took 3-4 years to become final release stable 1.0
even if it was useable without crash (for me) from 0.70...).
For me a stable freenet is much more use, than buggy version's with all
bell's and whistle's.
I have stopped using freenet as it uses too much of my machine's ressources
for almost nothing and i'm waiting till some people report it working.
Would it be possible to freeze freenet in the current state and write tests
for everything it is supposed to be doing and have them as a backup before
implementing new stuff ?
If testing is not possible because the stuff is too complicated, would
it be an idea to downgrade complexity for stability ?
At least my experience is, that if I write tests for my programs
- I'm sure they work as intended
- get error's where I forgot to implement a check or
change the source code
My programs are of course a lot smaller and do not use the
jvm at a level that I have to cope with jvm race conditions and
jvm bugs, that add a certain level of complexity, too.
I had the feeling, that freenet was becoming quite popular, but
it will drive people off, if the stable branch does not work as intended.
(and noone should recommend the unstable branch to a _user_ as he will
expect something useable).
Ciao
Jens Skripczynski
--
E-Mail: skripczynski(at)mail2003(dot)skripczynski(dot)de
There are only 10 types of people in this world:
those who understand binary and those who don't.
-- found in Norman Walsh signature
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
