I don't really see what's so unfortunate about that. Most admins
(including myself) go by the rule "If it ain't broken, don't fix it!"
Production systems, especially in companies are there to do something, and
that is not trying out the latest new gadgets out there. In my company,
out database server is *very* important and although downtime would not
cost us any money off hand, we wouldn't be able to serve our customers
anymore, since the information stored in there actually is the service we
provide.
I am very careful about trying out everything new out there, because
every update bears the risk of downtime. And both -STABLE, but especially
I'm not even sure we should board that train completely. Basicly,
RELENG_x_y is just that, but is could also be a good idea to have and
alternative. Something that is stable but can still be updated. Usually,
an update from one release to the next is relatively painless (major
releases excluded). I kept a machine running on RELENG_4 from 4.0-RELEASE
until now without ever having to change or reinstall the packages on it.
So it is possible. The next step would be to have something that updates
like RELENG_x but only uses tested and stable code like RELENG_x_y without
confining the user to a single release.
Regards
Chris
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
