On Wednesday 01 October 2003 07:50 am, Tracy R Reed wrote:
> Make a new release twice a week and twice a week only on a schedule.
> Tuesdays and Fridays for example. Why? Because...
Some people may _want_ bleeding edge, but your plan would be good for the 
Average Joe's releases.

> Last good build should ALWAYS be CURRENT_BUILD - 1. This way  brand new
> nodes will have someone to talk to but we will only be talking to the most
> recent or second most recent build. Freenet SHOULD have to be upgraded
> once a week. Freenet is still in the development phase and changing
> quickly. Anyone running freenet should be willing to maintain their node
> and upgrade at least once a week. Those people running ancient 5xxx series
> builds should be booted in the head for fscking up the network. Letting
> people run builds months old is accomplishing nothing since the network as
> it is is completely broken and makes it impossible to gauge performance of
> the new build when we have old builds DoS'ing us with tons of connections,
> bad routing, and other bugs. Yes, some people might not upgrade and the
> network might shrink. GREAT. We'll get better performance for it I'm
> willing to wager. A smaller network that works is better than a big
> network which doesn't. But I bet that as long as people know what to
> expect and expect regular upgrades once a week they will do the upgrades
> or even cron their system to shutdown freenet on Tuesdays and Fridays, run
> the update script, and start it up again.
Sometimes the new builds have horrible bugs that make older builds more usable 
for the client. There is not much way to prevent this. And what about Kaffe 
users?
-- 
"I love deadlines. I love the whooshing sound they make as they go by."
        - Douglas Adams
Nick Tarleton - [EMAIL PROTECTED] - PGP key available


_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to