From owner-freebsd-doc@freebsd.org Sun Oct 16 00:55:12 2016 Return-Path: Delivered-To: freebsd-doc@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 68491C06107 for ; Sun, 16 Oct 2016 00:55:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4D2277C5 for ; Sun, 16 Oct 2016 00:55:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G0tCDG029744 for ; Sun, 16 Oct 2016 00:55:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 213526] [patch] refactor Security page on website Date: Sun, 16 Oct 2016 00:55:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Website X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status keywords bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 00:55:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213526 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 Assignee: freebsd-doc@FreeBSD.org Reporter: linimon@FreeBSD.org Keywords: patch Created attachment 175809 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175809&action= =3Dedit 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 mode= ls 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 subheadin= gs, each with an entry in the new Table of Contents: * The TOC now switches places with Reporting FreeBSD Security Incidents, w= hich becomes the first entry in the TOC. (This is a little hard to see in the d= iff 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. T= he 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 Sup= port Model." Although the paragraphs are reordered, the content is mostly uncha= nged (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 Releas= es; Support Model. To me this makes the page flow much better, and assumes less knowledge on t= he part of a user unfamiliar with our procedures. --=20 You are receiving this mail because: You are the assignee for the bug.=