Date: Mon, 19 Apr 2004 17:45:39 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: henk@2complex.nl Cc: freebsd-questions@freebsd.org Subject: Re: cvsup stable Message-ID: <20040419164539.GB51066@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <000a01c42628$f84a9040$95f4153e@hilbrink.nl> References: <000a01c42628$f84a9040$95f4153e@hilbrink.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--WhfpMioaduB5tiZL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Apr 19, 2004 at 06:11:27PM +0200, henk@2complex.nl wrote:
> Hi all,
>=20
> I'd like to raise a question on cvsup.
> I'm an enthousiastic user of cvsup to keep up to date.
> I always use to stable-supfile
> Last week I installed a 4.9 machine ran a cvsup.
> Rebuilt the whole world and my kernel and ... ended up with
> 4.10 beta.
> A few aday later ran a cvsup again. Same story.
>=20
> I know FBSD is stable but do I have to rely beta's.
Ah... It's that time of year again. We get to do the whole 'what is
4-STABLE' thread for the umpteenth time.
Here's how it works: you're tracking the RELENG_4 code branch, which
gets you system version 4.x-STABLE -- well, most of the time.
Actually, that system version number and tag is pretty arbitrary.
It's just a snapshot out of the ever-evolving set of code which is the
RELENG_4 branch. Every so often the will be a new release made from
this branch. Usually something like 3 times a year. Around that
point the system version will go through all sorts of changes
relatively quickly. It will start as 4.9-STABLE, then become
4.10-BETA. After a while it will become 4.10-RC (as in 'Release
Candidate'), and maybe even 4.10-RC2. Eventually the release
engineering team will be satisfied, and the label will become
4.10-RELEASE. However, that only lasts for a vanishingly short time:
just long enough to create the RELENG_4_10 branch. Then the label
becomes 4.10-STABLE again for the next 3 months or so. (Well, actually
in this case, probably for ever after, as 4.10 is the last release
planned to be made from the RELENG_4 branch.)
Do not be alarmed by the what the label says. There are not massive
changes to the source code happening at the precise instant the the
change from -STABLE to -BETA is made. Those changes will have been
going into RELENG_4 continually throughout the preceeding months[1].
In fact, what -BETA signifies is an emphasis on testing and bug-fixing
rather than introducing new functionality. That means the -BETA code
is actually probably a bit more stable that the -STABLE code, although
there's really very little measurable difference. With all of the
testing being done, the code should reach a peak of perfection right
around the time that 4.10 is released, although (annoyingly) each
release does tend to generate a small flood of PRs and fixes
immediately *after* it happens.
Cheers,
Matthew
[1] If you find this alarming, then you should be tracking one of the
X.Y-RELEASE branches: those only get security and major bug fixes.
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--WhfpMioaduB5tiZL
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAhAIzdtESqEQa7a0RAq8pAJ4ksvwia7USIlYuMn1VcXzVVSJSFQCeO0dR
tuiQVnE2eJxdEEXBu4RFxX0=
=Q4fx
-----END PGP SIGNATURE-----
--WhfpMioaduB5tiZL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040419164539.GB51066>