From owner-svn-doc-all@freebsd.org Mon Sep 18 17:58:16 2017 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 1DC55E2275E; Mon, 18 Sep 2017 17:58:16 +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 CF3BC74697; Mon, 18 Sep 2017 17:58:15 +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 v8IHwFgu075542; Mon, 18 Sep 2017 17:58:15 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v8IHwE84075540; Mon, 18 Sep 2017 17:58:14 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201709181758.v8IHwE84075540@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Mon, 18 Sep 2017 17:58:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50871 - head/en_US.ISO8859-1/htdocs/releases/12.0R X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/releases/12.0R X-SVN-Commit-Revision: 50871 X-SVN-Commit-Repository: doc 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: Mon, 18 Sep 2017 17:58:16 -0000 Author: gjb Date: Mon Sep 18 17:58:14 2017 New Revision: 50871 URL: https://svnweb.freebsd.org/changeset/doc/50871 Log: Fix formatting to comply with FDP style guidelines. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/index.xml head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/12.0R/index.xml Mon Sep 18 17:46:57 2017 (r50870) +++ head/en_US.ISO8859-1/htdocs/releases/12.0R/index.xml Mon Sep 18 17:58:14 2017 (r50871) @@ -8,54 +8,47 @@ ]> - - &title; + + &title; - $FreeBSD$ - + $FreeBSD$ + - + -

Introduction

+

Introduction

-

This is the index page for &os; &local.rel;. For more - information about the release engineering process, please see the - Release Engineering section - of the web site.

+

This is the index page for &os; &local.rel;. For more + information about the release engineering process, please see + the Release Engineering + section of the web site.

-

Detailed Information

+

Detailed Information

-

More detailed information, such as release notes and hardware - notes can be found at these pages:

+

More detailed information, such as release notes and hardware + notes can be found at these pages:

- &os; &local.rel;-RELEASE signed checksum files
+ &os; &local.rel;-RELEASE signed checksum files
- &os; &local.rel;-RELEASE hardware information
+ &os; &local.rel;-RELEASE hardware information
- &os; &local.rel;-RELEASE release notes
+ &os; &local.rel;-RELEASE release notes
- &os; &local.rel;-RELEASE errata
+ &os; &local.rel;-RELEASE errata
- &os; &local.rel;-RELEASE readme
+ &os; &local.rel;-RELEASE readme
- &os; Release - Engineering TODO Page
- ?> + &os; Release + Engineering TODO Page
+ ?> - &os; &local.rel;-RELEASE schedule
- + &os; &local.rel;-RELEASE schedule
Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Mon Sep 18 17:46:57 2017 (r50870) +++ head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Mon Sep 18 17:58:14 2017 (r50871) @@ -11,219 +11,220 @@ ]> - - &title; + + &title; - $FreeBSD$ - + $FreeBSD$ + - + -

Introduction

+

Introduction

- This is the release schedule for &os; &local.rel;. For more - information about the release engineering process, please see the Release Engineering section of the - web site.

- ?> + This is the release schedule for &os; &local.rel;. For + more information about the release engineering process, please + see the Release + Engineering section of the web site.

+ ?> -

Although the &os; &local.rel; schedule has not yet been - written, the release cycle is currently anticipated to begin - around February 2019. This page will be updated accordingly if - this anticipated timeframe should change.

+

Although the &os; &local.rel; schedule has not yet been + written, the release cycle is currently anticipated to begin + around February 2019. This page will be updated accordingly if + this anticipated timeframe should change.

- General discussions about the pending release and known issues should be - sent to the public - freebsd-current mailing list. - MFC - requests should be sent to - re@FreeBSD.org.

+ General discussions about the pending release and known issues + should be sent to the public freebsd-current + mailing list. MFC + requests should be sent to re@FreeBSD.org.

- &beta.local.where; - &beta2.local.where; + &beta.local.where; + &beta2.local.where; -

Schedule

+

Schedule

-

During the &local.branch.head; freeze, the Release Engineering - Team may create ALPHA snapshots to publish for testing purposes. - As the frequency and total number of the ALPHA snapshots will - depend on the length of time the &local.branch.head; branch is - frozen, no official schedule is provided.

+

During the &local.branch.head; freeze, the Release Engineering + Team may create ALPHA snapshots to publish for testing purposes. + As the frequency and total number of the ALPHA snapshots will + depend on the length of time the &local.branch.head; branch is + frozen, no official schedule is provided.

-

Announcements regarding the availability of the - ALPHA snapshots will be sent to the freebsd-current - and freebsd-snapshots - mailing lists.

+

Announcements regarding the availability of the ALPHA snapshots + will be sent to the freebsd-current + and freebsd-snapshots + mailing lists.

- - - - - - - +
ActionExpectedActualDescription
+ + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - -
ActionExpectedActualDescription
Initial release schedule announcement--Release Engineers send announcement email to developers with - a rough schedule.
Initial release schedule announcement--Release Engineers send announcement email to developers + with a rough schedule.
Release schedule reminder--Release Engineers send reminder announcement e-mail to - developers with updated schedule.
Release schedule reminder--Release Engineers send reminder announcement e-mail to + developers with updated schedule.
Code slush begins--Release Engineers announce that all further commits to the - &local.branch.head; branch will not require explicit - approval, however new features should be avoided.
Code slush begins--Release Engineers announce that all further commits to the + &local.branch.head; branch will not require explicit + approval, however new features should be avoided.
Code freeze begins--Release Engineers announce that all further commits to the - &local.branch.head; branch will require explicit approval. - Certain blanket approvals will be granted for narrow areas of - development, documentation improvements, etc.
Code freeze begins--Release Engineers announce that all further commits to the + &local.branch.head; branch will require explicit approval. + Certain blanket approvals will be granted for narrow areas + of development, documentation improvements, etc.
KBI freeze begins--Release Engineers announce that all further commits to the - &local.branch.head; branch will require explicit approval. - Additionally, there can be no changes to the KBI until - &local.branch.head; is branched to &local.branch.stable;.
KBI freeze begins--Release Engineers announce that all further commits to the + &local.branch.head; branch will require explicit approval. + Additionally, there can be no changes to the KBI until + &local.branch.head; is branched to + &local.branch.stable;.
&local.branch.stable; branch--Subversion branch created; release engineering continues - on this branch.
&local.branch.stable; branch--Subversion branch created; release engineering continues + on this branch.
BETA1 builds begin--First beta test snapshot.
BETA1 builds begin--First beta test snapshot.
&local.branch.head; thaw--The code freeze on the &local.branch.head; branch - is lifted.
&local.branch.head; thaw--The code freeze on the &local.branch.head; branch + is lifted.
BETA2 builds begin--Second beta test snapshot.
BETA2 builds begin--Second beta test snapshot.
BETA3 builds begin --Third beta test snapshot.
BETA3 builds begin --Third beta test snapshot.
&local.branch.releng; branch--Subversion branch created; future release engineering - proceeds on this branch.
&local.branch.releng; branch--Subversion branch created; future release engineering + proceeds on this branch.
RC1 builds begin--First release candidate.
RC1 builds begin--First release candidate.
&local.branch.stable; thaw--The code freeze on the &local.branch.stable; branch - is lifted.
&local.branch.stable; thaw--The code freeze on the &local.branch.stable; branch + is lifted.
RC2 builds begin--Second release candidate.
RC2 builds begin--Second release candidate.
RC3 builds begin --Third release candidate.
RC3 builds begin --Third release candidate.
RELEASE builds begin--&local.rel;-RELEASE builds begin.
RELEASE builds begin--&local.rel;-RELEASE builds begin.
RELEASE announcement--&local.rel;-RELEASE press release.
RELEASE announcement--&local.rel;-RELEASE press release.
Turn over to the secteam--&local.branch.releng; branch is handed over to the - &os; Security Officer Team in one or two weeks after the - announcement.
+ + Turn over to the secteam + - + - + &local.branch.releng; branch is handed over to the + &os; Security Officer Team in one or two weeks after + the announcement. + + -

"*" indicates "as-needed" items.

+

"*" indicates "as-needed" items.

-

Status / TODO

- &os; Release - Engineering TODO Page - ?> +

Status / TODO

-

Additional Information

+ &os; Release + Engineering TODO Page + ?> - +

Additional Information

- +