>>>>> "MJR" == Mark J Roberts <[EMAIL PROTECTED]> writes:
MJR> Catch-22. We need support for the latest stuff in
MJR> freenetmirror so we can test the latest stuff.
OK, well, I guess I can branch freenetmirror. However, I'd like to
have a branch that runs with the stable version of Fred.
MJR> Shouldn't stable mean "We've tried this stuff for a week with
MJR> freenetmirror and it all seems to work."?
No, "stable" should mean, "This has been around for a while, we know
it works, and if it doesn't quite work, we'll fix it. It doesn't have
the latest bells and whistles, but you can count on it for building
apps or running your network."
"Stable" means just what it says: stable. NOT the latest-greatest-feature-
we-just-gotta-get-out-there-oh-jee-whillickers-once-we-have-this-one-
everybody-will-really-love-us. We can always have dev builds for
that. What "stable" does is give people some assurance that we're not
the Three Stooges with our thumbs in our asses.
Remember, 0.3.5 had broken KSK inserts. That meant that the BASIC
FUNCTIONALITY of Fred was broken in the official release for over a
month. The whole point of "stable" is so we can fix stuff like that
really quickly.
~Mr. Bad
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/\____/\ Mr. Bad <[EMAIL PROTECTED]>
\ / Pigdog Journal | http://pigdog.org/ | *Stay*Real*Bad*
| (X \x)
( ((**) "If it's not bad, don't do it.
\ <vvv> If it's not crazy, don't say it." - Ben Franklin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
