Date: Tue, 28 Oct 2003 15:17:14 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Jason Williams <jwilliams@courtesymortgage.com>, freebsd-questions@freebsd.org Subject: Re: Clarification on CVS Tags Message-ID: <p0600201fbbc47d4a8d2e@[128.113.24.47]> In-Reply-To: <5.2.1.1.0.20031028105856.00ac2ad0@pop.courtesymortgage.com> References: <5.2.1.1.0.20031028085609.00afa820@pop.courtesymortgage.com> <5.2.1.1.0.20031028085609.00afa820@pop.courtesymortgage.com> <5.2.1.1.0.20031028105856.00ac2ad0@pop.courtesymortgage.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:00 AM -0800 10/28/03, Jason Williams wrote:
>Thanks Matthew for your explanation. You answered a lot
>of my questions. Makes sense now really.
>
>Just out of curiosity, why would someone want to use:
>
>RELENG_4_8_0_RELEASE?
>
>Is there some type of benefit?
>One would think that the best option for production
>servers is:
>
>RELENG_4_8
>
>Thanks for your insight.
The "security" or "safe" branches (such as RELENG_4_8) are
relatively new. We still have to have tags such as
RELENG_4_8_0_RELEASE for the release process, and you
can use any tag for cvsup. Before the "security" branches
existed, we used to encourage people to upgrade to those
release-tags instead of upgrading to stable.
There are still times when you might want to cvsup to a
release point. Of course, once you do the buildworld
for that point, then you'll never see any new changes
until you switch to a different tag for cvsup.
For instance, it might be quite reasonable to cvsup to a
release tag, and once you know that worked you would then
cvsup to some later release tag, or to RELENG_4 ("stable").
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0600201fbbc47d4a8d2e>