----- Original Message -----
From: "Patrick M. Hausen" <[EMAIL PROTECTED]>
I have never ever had a single problem caused by running RELENG_N.
We changed that only because as the number of machines increases
it pays to run the same software on all of them, and "RELEASE"
provides a convenient (!) reference point for that. Yet, if I were
affected by a particular bug in RELENG_6_3, I would simply pick
my own later reference point at which the bug is fixed.
An alternative to this is to maintain a specific set of patches
to -RELEASE for only the issues / fixes that you are experiencing.
This has worked very well for us over the years so I can recommend
it as well.
Either way you get stable release which you can test and certify
in your own environment, keeping regression risks to an absolute
minimum.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
