Add the initial schedule for 12.0-RELEASE.

Add 12.0 to the releng index page, and the main index page.

Approved by:	re (implicit)
Sponsored by:	The FreeBSD Foundation

en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml

@@ -21,19 +21,11 @@
 
     <h1>Introduction</h1>
 
-    <?ignore
     <p>This is the release schedule for &os;&nbsp;&local.rel;.  For
       more information about the release engineering process, please
       see the <a href="&base;/releng/index.html">Release
 	Engineering</a> section of the web site.</p>
-    ?>
 
-    <p>Although the &os;&nbsp;&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.</p>
-
-    <?ignore
     <p>General discussions about the pending release and known issues
       should be sent to the public <a
 	href="mailto:FreeBSD-current@FreeBSD.org">freebsd-current</a>
@@ -71,14 +63,14 @@
       <tr>
 	<td>Initial release schedule announcement</td>
 	<td>-</td>
-	<td>-</td>
+	<td>24&nbsp;April&nbsp;2018</td>
 	<td>Release Engineers send announcement email to developers
 	  with a rough schedule.</td>
       </tr>
 
       <tr>
 	<td>Release schedule reminder</td>
-	<td>-</td>
+	<td>6&nbsp;July&nbsp;2018</td>
 	<td>-</td>
 	<td>Release Engineers send reminder announcement e-mail to
 	  developers with updated schedule.</td>
@@ -86,7 +78,7 @@
 
       <tr>
 	<td>Code slush begins</td>
-	<td>-</td>
+	<td>10&nbsp;August&nbsp;2018</td>
 	<td>-</td>
 	<td>Release Engineers announce that all further commits to the
 	  &local.branch.head; branch will not require explicit
@@ -95,7 +87,7 @@
 
       <tr>
 	<td>Code freeze begins</td>
-	<td>-</td>
+	<td>24&nbsp;August&nbsp;2018</td>
 	<td>-</td>
 	<td>Release Engineers announce that all further commits to the
 	  &local.branch.head; branch will require explicit approval.
@@ -105,7 +97,7 @@
 
       <tr>
 	<td>KBI freeze begins</td>
-	<td>-</td>
+	<td>7&nbsp;September&nbsp;2018</td>
 	<td>-</td>
 	<td>Release Engineers announce that all further commits to the
 	  &local.branch.head; branch will require explicit approval.
@@ -116,7 +108,7 @@
 
       <tr>
 	<td>&local.branch.stable; branch</td>
-	<td>-</td>
+	<td>21&nbsp;September&nbsp;2018</td>
 	<td>-</td>
 	<td>Subversion branch created; release engineering continues
 	  on this branch.</td>
@@ -124,14 +116,14 @@
 
       <tr>
 	<td>BETA1 builds begin</td>
-	<td>-</td>
+	<td>21&nbsp;September&nbsp;2018</td>
 	<td>-</td>
 	<td>First beta test snapshot.</td>
       </tr>
 
       <tr>
 	<td>&local.branch.head;&nbsp;thaw</td>
-	<td>-</td>
+	<td>23&nbsp;September&nbsp;2018</td>
 	<td>-</td>
 	<td>The code freeze on the &local.branch.head; branch
 	  is lifted.</td>
@@ -139,21 +131,21 @@
 
       <tr>
 	<td>BETA2 builds begin</td>
-	<td>-</td>
+	<td>28&nbsp;September&nbsp;2018</td>
 	<td>-</td>
 	<td>Second beta test snapshot.</td>
       </tr>
 
       <tr>
 	<td>BETA3 builds begin&nbsp;*</td>
-	<td>-</td>
+	<td>5&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>Third beta test snapshot.</td>
       </tr>
 
       <tr>
 	<td>&local.branch.releng; branch</td>
-	<td>-</td>
+	<td>12&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>Subversion branch created; future release engineering
 	  proceeds on this branch.</td>
@@ -161,14 +153,14 @@
 
       <tr>
 	<td>RC1 builds begin</td>
-	<td>-</td>
+	<td>12&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>First release candidate.</td>
       </tr>
 
       <tr>
 	<td>&local.branch.stable;&nbsp;thaw</td>
-	<td>-</td>
+	<td>14&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>The code freeze on the &local.branch.stable; branch
 	  is lifted.</td>
@@ -176,28 +168,28 @@
 
       <tr>
 	<td>RC2 builds begin</td>
-	<td>-</td>
+	<td>19&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>Second release candidate.</td>
       </tr>
 
       <tr>
 	<td>RC3 builds begin&nbsp;*</td>
-	<td>-</td>
+	<td>26&nbsp;October&nbsp;2018</td>
 	<td>-</td>
 	<td>Third release candidate.</td>
       </tr>
 
       <tr>
 	<td>RELEASE builds begin</td>
-	<td>-</td>
+	<td>2&nbsp;November&nbsp;2018</td>
 	<td>-</td>
 	<td>&local.rel;-RELEASE builds begin.</td>
       </tr>
 
       <tr>
 	<td>RELEASE announcement</td>
-	<td>-</td>
+	<td>6&nbsp;November&nbsp;2018</td>
 	<td>-</td>
 	<td>&local.rel;-RELEASE press release.</td>
       </tr>
@@ -214,6 +206,7 @@
 
     <p>&quot;*&quot; indicates &quot;as-needed&quot; items.</p>
 
+    <?ignore
     <h1>Status / TODO</h1>
 
     <a href="&base;/releases/&local.rel;R/todo.html">&os; Release

en_US.ISO8859-1/htdocs/releng/index.xml

@@ -61,6 +61,14 @@
 	  href="&base;/releases/11.2R/schedule.html">Target
 	  Schedule</a></td>
     </tr>
+
+    <tr>
+      <td>November&nbsp;2018</td>
+      <td>&os;&nbsp;12.0</td>
+      <td><a
+	  href="&base;/releases/12.0R/schedule.html">Target
+	  Schedule</a></td>
+    </tr>
   </table>
 
   <h2><a name="freeze" id="freeze">Code-Freeze Status</a></h2>

share/xml/release.ent

@@ -48,14 +48,14 @@
       are having release candidates at the same time), do the same here.  -->
 
 <!-- Set to 'INCLUDE' when the schedule is available. -->
-<!ENTITY beta2.upcoming "IGNORE">
+<!ENTITY beta2.upcoming "INCLUDE">
 <!ENTITY % beta2.upcoming "IGNORE">
 
 <!-- Set to 'INCLUDE' when the installation images are available. -->
 <!ENTITY beta2.testing "IGNORE">
 <!ENTITY % beta2.testing "IGNORE">
-<!ENTITY betarel2.current '10.4'>
-<!ENTITY betarel2.vers 'RC2'>
+<!ENTITY betarel2.current '12.0'>
+<!ENTITY betarel2.vers 'RELEASE'>
 <!ENTITY u.betarel2.schedule '&base;/releases/&betarel2.current;R/schedule.html'>
 
 <!ENTITY rel.current.major '11'>