os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a footnote admitting that we can't support old versions of FreeBSD

Browse source 
forever, and point the user to freebsd.org/security for more
information about which branches/releases are currently supported.

PR:		docs/29182
Submitted by:	Tony Fleisher <takhus@takhus.mind.net>
This commit is contained in:
Murray Stokely 2001-09-02 22:25:56 +00:00
parent f1979ede58
commit a90b86c541
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10546
1 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.86 2001/08/19 23:46:43 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.87 2001/08/22 06:53:19 murray Exp $
-->
<chapter id="cutting-edge">
@ -312,7 +312,15 @@ subscribe cvs-all</programlisting>
&os.stable; branch, you do not <emphasis>need</emphasis> 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
affects
<footnote><para>That's not quite true. We can't continue to
support old releases of FreeBSD forever, although we do
support them for many years. For a complete description
of the current security policy for old releases of
FreeBSD, please see <ulink
url="http://www.FreeBSD.org">http://www.FreeBSD.org/security</ulink></para>
</footnote>
, and tracking an entire development branch just
for security reasons is likely to bring in a lot of unwanted
changes as well.</para>