From owner-freebsd-questions@FreeBSD.ORG  Tue Apr 12 09:15:07 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0F0B316A4CE
	for <freebsd-questions@freebsd.org>;
	Tue, 12 Apr 2005 09:15:07 +0000 (GMT)
Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BA5A143D54
	for <freebsd-questions@freebsd.org>;
	Tue, 12 Apr 2005 09:15:06 +0000 (GMT)
	(envelope-from infofarmer@mail.ru)
Received: from [83.237.195.182] (port=4268 helo=[172.17.0.69])
	by mx2.mail.ru with asmtp 
	id 1DLHU9-000KkA-00; Tue, 12 Apr 2005 13:15:05 +0400
Message-ID: <425B919D.9030408@mail.ru>
Date: Tue, 12 Apr 2005 13:15:09 +0400
From: "Andrew P." <infofarmer@mail.ru>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: glyn@millingtons.org
References: <86hdicihey.fsf@nowhere.org>
In-Reply-To: <86hdicihey.fsf@nowhere.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-questions@freebsd.org
Subject: Re: Best upgrade strategy
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: infofarmer@mail.ru
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2005 09:15:07 -0000

Glyn Millington wrote:
> That is fine, but at the point when 5.4 becomes the production release, I
> would like simply to track that for security fixes etc rather than follow
> the stable developement branch.
> 
> Can I acheive that simply by putting
> 
> *default release=cvs tag=RELENG_5_4
> 
> into my cvsup file, at the right time -ie as soon as 5.4 becomes
> a production release? ?  Or will there be such
> complications that it would be best to perform yet another install (which
> is smooth but slow on my set-up).


Yes, you can use RELENG_5_4 tag to track
security fixes when 5.4 is released. It
goes smoothly most of the times, some
people even managed to upgrade from
4.x to 5.x without reinstalling (ok,
_that_ wasn't smooth). Just look through
release notes, src/UPDATING and so on,
and use mergemaster carefully.


Best wishes,
Andrew P.