Hmm, this brings up another interesting question. First, to put this in
context:
Jordan K. Hubbard wrote:
> Actually, the -missioncritical branch is sort of provided for
> now as a function of -previousstable. There are plenty of people still
> running 2.2.x, for example, and you even still occasionally see commits
> to the 2.2.x branch.
And, Colin wrote:
> My point is, if a new release every quarter scares you, upgrade
> once/year (except bugfixes/security patches) and get on with your life.
> I used 3.0 for several months and life was good, and it still runs on
> one of my machines. I upgraded this one for several reasons that were
> specific to me, your requirements will vary.
Ok, so, let's assume I JUST want to incorporate bugfixes into the -RELEASE
(be it 3.x or whatever) that I have on a particular machine. How would I
go about doing this?
I have machines all the way from 2.2.2-RELEASE through 3.3-RELEASE, and
even one I track -STABLE on (for both development of a PicoBSD-based
"product" I am doing and also to keep the OS up to date).
It would be nice to leave the 3.x machines "alone" except for bugfixes.
The 2.2.2-RELEASE machine has been ignored for a LONG time as it would be
a pain to upgrade/rebuild. I plan on replacing it this month.
- Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com
Solutions for your high-tech problems. (406)-442-6648
----------------------------------------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
