From pepper@reppep.com  Mon Jan 19 16:57:13 2004
Return-Path: <pepper@reppep.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id ED63316A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Jan 2004 16:57:13 -0800 (PST)
Received: from www.reppep.com (www.reppep.com [66.92.104.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 36B2243D45
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Jan 2004 16:57:11 -0800 (PST)
	(envelope-from pepper@reppep.com)
Received: by www.reppep.com (Postfix, from userid 501)
	id 5D8DBFE82; Mon, 19 Jan 2004 19:58:05 -0500 (EST)
Message-Id: <20040120005805.5D8DBFE82@www.reppep.com>
Date: Mon, 19 Jan 2004 19:58:05 -0500 (EST)
From: Chris Pepper <pepper@reppep.com>
Reply-To: Chris Pepper <pepper@reppep.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html should be updated with info on updating 5.2 w/o HEAD
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         61598
>Category:       docs
>Synopsis:       http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html should be updated with info on updating 5.2 w/o HEAD
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan 19 17:00:09 PST 2004
>Closed-Date:    Thu Jun 03 03:27:10 PDT 2004
>Last-Modified:  Thu Jun 03 03:27:10 PDT 2004
>Originator:     Chris Pepper
>Release:        FreeBSD 4.9-STABLE i386
>Organization:
>Environment:
System: FreeBSD www.reppep.com 4.9-STABLE FreeBSD 4.9-STABLE #13: Thu Nov 13 23:50:39 EST 2003 root@www.reppep.com:/usr/obj/usr/src/sys/REPPEP i386


	
>Description:
	The Handbook, in particular http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html, lacks information on updating 5.2. I'm testing the water, after tracking 4_RELENG for a while, and don't want to use CURRENT, but nformation on the equivalent to RELENG_4 is hard to find. I see RELENG_5_2 in cvsweb -- is there something else I should track to keep 5.2 updated without going fully bleeding-edge? This should also probably be mentioned in the FAQ.

	Similarly, http://www.freebsd.org/releng/ should be updated (the HEAD comment says 5.2 is not yet announced).
	
>How-To-Repeat:
	Visit the mentioned URLs.
	
>Fix:
	Update these URLs with information on tracking 5.2 -- is RELENG_5_2 only for security fixes, comparable to RELENG_4_8? Is there any alternative to track aside from CURRENT (tag=.)?
>Release-Note:
>Audit-Trail:

From: Peter Pentchev <roam@ringlet.net>
To: Chris Pepper <pepper@reppep.com>
Cc: bug-followup@FreeBSD.org
Subject: Re: docs/61598: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html should be updated with info on updating 5.2 w/o HEAD
Date: Fri, 23 Apr 2004 18:14:54 +0300

 --cQXOx3fnlpmgJsTP
 Content-Type: text/plain; charset=windows-1251
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Jan 19, 2004 at 07:58:05PM -0500, Chris Pepper wrote:
 > >Description:
 > 	The Handbook, in particular
 > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html,
 > lacks information on updating 5.2.
 > I'm testing the water, after tracking 4_RELENG for a while, and don't
 > want to use CURRENT, but nformation on the equivalent to RELENG_4 is
 > hard to find. I see RELENG_5_2 in cvsweb -- is there something else I
 > should track to keep 5.2 updated without going fully bleeding-edge?
 > This should also probably be mentioned in the FAQ.
 
 No, there is no such branch for the present.  Currently, the only 5.x
 branches available are HEAD (the bleeding-edge -CURRENT itself) and the
 release branches (or security branches) RELENG_5_0, RELENG_5_1,
 RELENG_5_2, RELENG_5_2_1.  None of them has the semantics of a stable
 branch because, well, 5.x is not yet deemed stable.  When the transition
 to 5.x-STABLE is made, a new RELENG_5 branch will be created and it will
 then have the same 'stable branch' semantics as the current RELENG_4.
 This will most likely happen with the release of FreeBSD 5.3 in a couple
 of months.
 
 > 	Similarly, http://www.freebsd.org/releng/ should be updated (the
 > HEAD comment says 5.2 is not yet announced).
 
 I think this has happened in the meantime :)
 
 > >Fix:
 
 > 	Update these URLs with information on tracking 5.2 -- is
 > RELENG_5_2 only for security fixes, comparable to RELENG_4_8? Is
 > there any alternative to track aside from CURRENT (tag=3D.)?
 
 No, there is no alternative yet.  As explained above, the RELENG_5
 (stable) branch will probably be cut with FreeBSD 5.3.  For the present,
 yes, there is only the release branch RELENG_5_2, which only carries
 security fixes.
 
 Thus, there doesn't seem to be anything that would need updating on the
 above URL's, except the updates that have already been done as things
 progressed with the release of 5.2.1 and the upcoming 4.10 :)
 
 G'luck,
 Peter
 
 --=20
 Peter Pentchev	roam@ringlet.net    roam@sbnd.net    roam@FreeBSD.org
 PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
 If I had finished this sentence,
 
 --cQXOx3fnlpmgJsTP
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFAiTLt7Ri2jRYZRVMRAn+HAJ4kWLLNdhZh/faBHs2GsRyEbDDPrACgtmEZ
 0V4TaANTRHUjjjrjnom3JCo=
 =FyRx
 -----END PGP SIGNATURE-----
 
 --cQXOx3fnlpmgJsTP--
State-Changed-From-To: open->closed 
State-Changed-By: roam 
State-Changed-When: Thu Jun 3 03:23:43 PDT 2004 
State-Changed-Why:  
Feedback timeout of sorts. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61598 
>Unformatted:
