Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2001 18:49:09 -0500
From:      Bill Moran <wmoran@mail.iowna.com>
To:        Kris Kennaway <kris@FreeBSD.ORG>
Cc:        Cliff Sarginson <cliff@raggedclown.net>, questions@FreeBSD.ORG
Subject:   Re: I am confused about tracking stable
Message-ID:  <3A68D275.BB416780@mail.iowna.com>
References:  <01012000204800.03036@buffy> <20010119154538.A13324@citusc17.usc.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote:
> 
> On Sat, Jan 20, 2001 at 12:20:48AM +0100, Cliff Sarginson wrote:
> > Hello
> > I have a 4.0 RELEASE installation.
> > Is tracking STABLE meaningful, since the latest release is 4.2
> 
> Imagine 4.x-RELEASE a single point along a long line called "FreeBSD
> 4.x-STABLE". In other words, every now and then we take a snapshot of
> the current state of the 4.x branch, and call it 4.y-RELEASE. The name
> "4.x-STABLE" means "the 4.x branch after the release of 4.x-RELEASE
> but before 4.(x+1)-RELEASE". So the only difference between
> 4.0-RELEASE and 4.2-RELEASE is that the latter is a much newer version
> of the 4.x codebase. So what you want is in fact to update to
> 4.2-STABLE.

As a side note, it is possible (should you want to ) to update to the
last 4.1-STABLE that existed before 4.2-RELEASE was announced. Read the
man pages on cvsup.
However, I don't personally see the use in this, if you're going to
upgrade, go to the latest 4.x version.

The reason I use it is for updating my production servers. I have a test
machine that I update to the latest -STABLE, and then test for a week.
If everything goes fine, I then upgrade any production servers I want to
upgrade to that EXACT version that I tested (using date tags.) Paranoid,
I know, but I'm too lazy to fix things after the fact.

-Bill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A68D275.BB416780>