From owner-svn-doc-all@freebsd.org Tue Oct 25 16:44:28 2016 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65FA3C21421; Tue, 25 Oct 2016 16:44:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 407A697D; Tue, 25 Oct 2016 16:44:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u9PGiRjO064614; Tue, 25 Oct 2016 16:44:27 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u9PGiRgl064613; Tue, 25 Oct 2016 16:44:27 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201610251644.u9PGiRgl064613@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 25 Oct 2016 16:44:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49580 - head/en_US.ISO8859-1/htdocs/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 16:44:28 -0000 Author: gjb Date: Tue Oct 25 16:44:27 2016 New Revision: 49580 URL: https://svnweb.freebsd.org/changeset/doc/49580 Log: Make igor(1) less unhappy about security.xml. Translators can ignore, this is whitespace-only. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/security/security.xml Modified: head/en_US.ISO8859-1/htdocs/security/security.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/security/security.xml Tue Oct 25 16:38:42 2016 (r49579) +++ head/en_US.ISO8859-1/htdocs/security/security.xml Tue Oct 25 16:44:27 2016 (r49580) @@ -89,19 +89,19 @@ which is primarily oriented towards &os; developers.)

    -

  • The -STABLE branch tags have - names like stable/10. The corresponding builds have - names like FreeBSD 10.1-STABLE.

    • +

  • The -STABLE branch tags have names like stable/10. + The corresponding builds have names like FreeBSD + 10.1-STABLE.

  • Each FreeBSD Release has an associated Security Branch. - The Security Branch tags have names like releng/10.1. + The Security Branch tags have names like releng/10.1. The corresponding builds have names like FreeBSD 10.1-RELEASE-p4.

-

Issues affecting the FreeBSD Ports Collection are covered separately in the FreeBSD VuXML - document.

+

Issues affecting the FreeBSD Ports Collection are covered + separately in the FreeBSD + VuXML document.

How to update your system

@@ -210,8 +210,8 @@ -

In the run-up to a release, a number of -BETA - and -RC releases may be published for testing purposes. These releases are only +

In the run-up to a release, a number of -BETA and -RC releases + may be published for testing purposes. These releases are only supported for a few weeks, as resources permit, and will not be listed as supported on this page. Users are strongly discouraged from running these releases on production systems.

@@ -229,9 +229,9 @@ release.

The details and rationale behind this change can be found in the - official - announcement sent in February 2015.

+ official + announcement sent in February 2015.

Previously, branches were designated as either Normal or Extended. The designation was used as a guideline for @@ -240,18 +240,18 @@

Normal
Releases which are published from a -STABLE branch were - supported by the Security Officer for a minimum of 12 months after the - release, and for sufficient additional time (if needed) to ensure - that there is a newer release for at least 3 months before the - older Normal release expires. + supported by the Security Officer for a minimum of 12 months + after the release, and for sufficient additional time (if + needed) to ensure that there is a newer release for at least + 3 months before the older Normal release expires.
Extended
Selected releases (normally every second release plus the last - release from each -STABLE branch) were supported by the - Security Officer for a minimum of 24 months after the release, - and for sufficient additional time (if needed) to ensure that - there is a newer Extended release for at least 3 months before the - older Extended release expires. + release from each -STABLE branch) were supported by the Security + Officer for a minimum of 24 months after the release, and for + sufficient additional time (if needed) to ensure that there is + a newer Extended release for at least 3 months before the older + Extended release expires.