Bug ID: 213526
           Summary: [patch] refactor Security page on website
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Many People
          Priority: ---
         Component: Website
          Keywords: patch

Created attachment 175809
major patch to security/security.xml

This is part 3 of 3 different patches to the Security page on the website.  It
is the most intrusive one.

There are two parts to this: the content changes, and the reordering.

The content changes are to reflect the fact that two different support models
are defined in the page.  The text mostly stays the same, but is reworded to
reflect, in order, "here is what the support model is now; but FYI, here is
what the support model was previously".

The reordering changes consolidate existing text but adds more h2 subheadings,
each with an entry in the new Table of Contents:

 * The TOC now switches places with Reporting FreeBSD Security Incidents, which
becomes the first entry in the TOC.  (This is a little hard to see in the diff
due to the other changes in the TOC.)

 * The next two items become Recent FreeBSD Security Advisories and
Understanding FreeBSD Security Advisories.  The former existed as such; the
latter text was buried down at the bottom of the page and had no header.  The
text itself is mostly unchanged (see above).

 * The next section continues to be "How To Update Your System".

 * The next section continues to be "Supported Releases".  However, the
paragraph including "the support model has been changed" and the 2 after it are
moved below "Supported Releases" into a new section called "The FreeBSD Support
Model."  Although the paragraphs are reordered, the content is mostly unchanged
(see above).

 * The last section is the new "The FreeBSD Support Model", which only
consolidates existing content.

So the overall page flow is: Security Incidents; Updating; Supported Releases;
Support Model.

To me this makes the page flow much better, and assumes less knowledge on the
part of a user unfamiliar with our procedures.

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to