svn commit: r51587 - in head: en_US.ISO8859-1/htdocs/releases/12.0R en_US.ISO8859-1/htdocs/releng share/xml
Glen Barber
gjb at FreeBSD.org
Thu Apr 26 15:47:37 UTC 2018
Author: gjb
Date: Thu Apr 26 15:47:35 2018
New Revision: 51587
URL: https://svnweb.freebsd.org/changeset/doc/51587
Log:
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
Modified:
head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml
head/en_US.ISO8859-1/htdocs/releng/index.xml
head/share/xml/release.ent
Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Tue Apr 24 00:57:52 2018 (r51586)
+++ head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Thu Apr 26 15:47:35 2018 (r51587)
@@ -21,19 +21,11 @@
<h1>Introduction</h1>
- <?ignore
<p>This is the release schedule for &os; &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; &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 at FreeBSD.org">freebsd-current</a>
@@ -71,23 +63,23 @@
<tr>
<td>Initial release schedule announcement</td>
<td>-</td>
- <td>-</td>
+ <td>24 April 2018</td>
<td>Release Engineers send announcement email to developers
with a rough schedule.</td>
</tr>
<tr>
<td>Release schedule reminder</td>
+ <td>6 July 2018</td>
<td>-</td>
- <td>-</td>
<td>Release Engineers send reminder announcement e-mail to
developers with updated schedule.</td>
</tr>
<tr>
<td>Code slush begins</td>
+ <td>10 August 2018</td>
<td>-</td>
- <td>-</td>
<td>Release Engineers announce that all further commits to the
&local.branch.head; branch will not require explicit
approval, however new features should be avoided.</td>
@@ -95,8 +87,8 @@
<tr>
<td>Code freeze begins</td>
+ <td>24 August 2018</td>
<td>-</td>
- <td>-</td>
<td>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
@@ -105,8 +97,8 @@
<tr>
<td>KBI freeze begins</td>
+ <td>7 September 2018</td>
<td>-</td>
- <td>-</td>
<td>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
@@ -116,89 +108,89 @@
<tr>
<td>&local.branch.stable; branch</td>
+ <td>21 September 2018</td>
<td>-</td>
- <td>-</td>
<td>Subversion branch created; release engineering continues
on this branch.</td>
</tr>
<tr>
<td>BETA1 builds begin</td>
+ <td>21 September 2018</td>
<td>-</td>
- <td>-</td>
<td>First beta test snapshot.</td>
</tr>
<tr>
<td>&local.branch.head; thaw</td>
+ <td>23 September 2018</td>
<td>-</td>
- <td>-</td>
<td>The code freeze on the &local.branch.head; branch
is lifted.</td>
</tr>
<tr>
<td>BETA2 builds begin</td>
+ <td>28 September 2018</td>
<td>-</td>
- <td>-</td>
<td>Second beta test snapshot.</td>
</tr>
<tr>
<td>BETA3 builds begin *</td>
+ <td>5 October 2018</td>
<td>-</td>
- <td>-</td>
<td>Third beta test snapshot.</td>
</tr>
<tr>
<td>&local.branch.releng; branch</td>
+ <td>12 October 2018</td>
<td>-</td>
- <td>-</td>
<td>Subversion branch created; future release engineering
proceeds on this branch.</td>
</tr>
<tr>
<td>RC1 builds begin</td>
+ <td>12 October 2018</td>
<td>-</td>
- <td>-</td>
<td>First release candidate.</td>
</tr>
<tr>
<td>&local.branch.stable; thaw</td>
+ <td>14 October 2018</td>
<td>-</td>
- <td>-</td>
<td>The code freeze on the &local.branch.stable; branch
is lifted.</td>
</tr>
<tr>
<td>RC2 builds begin</td>
+ <td>19 October 2018</td>
<td>-</td>
- <td>-</td>
<td>Second release candidate.</td>
</tr>
<tr>
<td>RC3 builds begin *</td>
+ <td>26 October 2018</td>
<td>-</td>
- <td>-</td>
<td>Third release candidate.</td>
</tr>
<tr>
<td>RELEASE builds begin</td>
+ <td>2 November 2018</td>
<td>-</td>
- <td>-</td>
<td>&local.rel;-RELEASE builds begin.</td>
</tr>
<tr>
<td>RELEASE announcement</td>
+ <td>6 November 2018</td>
<td>-</td>
- <td>-</td>
<td>&local.rel;-RELEASE press release.</td>
</tr>
@@ -214,6 +206,7 @@
<p>"*" indicates "as-needed" items.</p>
+ <?ignore
<h1>Status / TODO</h1>
<a href="&base;/releases/&local.rel;R/todo.html">&os; Release
Modified: head/en_US.ISO8859-1/htdocs/releng/index.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/releng/index.xml Tue Apr 24 00:57:52 2018 (r51586)
+++ head/en_US.ISO8859-1/htdocs/releng/index.xml Thu Apr 26 15:47:35 2018 (r51587)
@@ -61,6 +61,14 @@
href="&base;/releases/11.2R/schedule.html">Target
Schedule</a></td>
</tr>
+
+ <tr>
+ <td>November 2018</td>
+ <td>&os; 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>
Modified: head/share/xml/release.ent
==============================================================================
--- head/share/xml/release.ent Tue Apr 24 00:57:52 2018 (r51586)
+++ head/share/xml/release.ent Thu Apr 26 15:47:35 2018 (r51587)
@@ -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'>
More information about the svn-doc-all
mailing list