From 125ae35cfc86d96cab9e478589012328361e916f Mon Sep 17 00:00:00 2001 From: "Jordan K. Hubbard" Date: Mon, 23 Jul 2001 08:27:37 +0000 Subject: [PATCH] Further strengthen the wording of Nik's revisions for -stable, making it very clear that this is _not_ a branch for end-users, it is for developers. --- .../books/handbook/cutting-edge/chapter.sgml | 33 +++++++++++-------- 1 file changed, 19 insertions(+), 14 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml index bb2f641176..e9748478a8 100644 --- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml @@ -1,7 +1,7 @@ @@ -264,26 +264,31 @@ subscribe cvs-all What is &os.stable;? -STABLE - &os.stable; is our development branch for a more low-key - and conservative set of changes intended for our next mainstream - release. Any changes to this branch will have debuted in - &os.current; first, helping to reduce (but not eliminate) the chance - that the changes will cause problems. + &os.stable; is our development branch from which major releases + are made. Changes go into this branch at a different pace, and + with the general assumption that they've first gone into + &os.current; first for testing. This is still + a development branch, however, and this means that at any given time, + the sources for &os.stable; may or may not be suitable for any + particular purpose. It is simply another engineering development + track, not a resource for end-users. Who needs &os.stable;? - If you are interested in tracking the FreeBSD development - process, and you want early access to the features that will appear - in the next point release of FreeBSD then you should + If you are interested in tracking or contributing to the + FreeBSD development process, especially as it relates to the + next point release of FreeBSD, then you should consider following &os.stable;. - Tracking &os.stable; also gives you easy access to security - fixes for FreeBSD as they are released. However, you do not - need to track &os.stable; to do this, as every - security advisory for FreeBSD explains how to fix the problem for - the releases it affects. + While it is true that security fixes also go into the + &os.stable; branch, you do not need to + track &os.stable; to do this. Every security advisory for + FreeBSD explains how to fix the problem for the releases it + affects, and tracking an entire development branch just + for security reasons is likely to bring in a lot of unwanted + changes as well. Although we endeavor to ensure that the &os.stable; branch compiles and runs at all times, this cannot be guaranteed. In