From owner-freebsd-stable Wed Jun 27 9: 8: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (tserver.conference.usenix.org [199.103.159.3]) by hub.freebsd.org (Postfix) with ESMTP id 49E0737B409; Wed, 27 Jun 2001 09:07:56 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f5R0QLQ05659; Wed, 27 Jun 2001 01:26:21 +0100 (BST) (envelope-from nik) Date: Wed, 27 Jun 2001 01:26:20 +0100 From: Nik Clayton To: Christopher Schulte Cc: Nik Clayton , Juha Saarinen , "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627012620.B5408@canyon.nothing-going-on.org> References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> <5.1.0.14.0.20010627093802.03cf0308@pop.schulte.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.0.20010627093802.03cf0308@pop.schulte.org>; from christopher@schulte.org on Wed, Jun 27, 2001 at 09:41:18AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 27, 2001 at 09:41:18AM -0500, Christopher Schulte wrote: >=20 > At 11:44 PM 6/26/2001 +0100, Nik Clayton wrote: > >I've rewritten section 19.2.2.1 and 19.2.2.2 at > > > >=20 > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable= .html > > > >Do people think this gets the point across any better? >=20 > The patch branch (currently RELENG_4_3) should be introduced, perhaps=20 > mentioned here,=20 Not yet. AIUI, the RELENG_4_3 branch is an experiment, and gives us the option of providing security fixes this way. I haven't seen a commitment[1] from the security officer team that they will actually do this. Until that happens I don't think it should be documented. N [1] Not a slur on the fine efforts of the security team. I mean that I haven't seen an e-mail that says "Yes, any security fixes to RELENG_4 will *definitely* be made available on the RELENG_4_3 branch". --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjs5KCsACgkQk6gHZCw343VX4QCcCi1sUSoNpCIJu848pYAij5uh fPUAn15q2sUkD4j7tAJaVnbpzW4wUAHj =lfwm -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message