Date: Thu, 21 Jun 2001 12:14:55 +0200 From: Christoph Sold <so@server.i-clue.de> To: Nuno Teixeira <nuno.mailinglists@pt-quorum.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Staying *really stable* in FreeBSD Message-ID: <3B31C91F.E330179E@i-clue.de> References: <20010620232046.P486-100000@gateway.bogus>
next in thread | previous in thread | raw e-mail | index | archive | help
Nuno Teixeira schrieb: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > I have been follow the discussion about RELEASE, STABLE, CURRENT and > security patches for a particular release. > > Resuming: RELEASE and STABLE are develoment branches. > > In the handbook related to STABLE: «but we do occasionally make > mistakes», so the best whay to stay really STABLE is do something like: > > cvsup to the last release RELENG_4_3_0_RELEASE and then cvsup all the > times to RELENG_4_3 to receive security and critical fixes only. > > Am I right? Yes. > When the RELEASE 4.4(?) is out, then I should repeat the example above to: > > RELENG_4_4_0_RELEASE > and then stay in > RELENG_4_4 > > Am I right? As I understand, you just have to cvsup to RELENG_4_4 -- the very first tag with this name will be the release. > For what I read in this mailing list related to the naming version, is > that the name STABLE make confusion some times (like in this particular > case). Well, staying stable may sometimes be adventurous (see the docs tree at this time), but overall, I never had any problems with it -- given I install on machines out of production, test them, then move them into production and never touch them until moved out of production again. Just my EUR.02 -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B31C91F.E330179E>