svn commit: r49852 - head/en_US.ISO8859-1/htdocs/news/status

Sat Jan 14 23:36:47 UTC 2017

Author: bjk
Date: Sat Jan 14 23:36:46 2017
New Revision: 49852
URL: https://svnweb.freebsd.org/changeset/doc/49852

Log:
  Add re@ entry from gjb

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml	Sat Jan 14 22:45:38 2017	(r49851)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml	Sat Jan 14 23:36:46 2017	(r49852)
@@ -1060,4 +1060,43 @@
 	<tt>bhyve</tt> and attached to an RBD image.</task>
     </help>
   </project>
+
+  <project cat='team'>
+    <title>&os; Release Engineering Team</title>
+
+    <contact>
+      <person>
+	<name>&os; Release Engineering Team</name>
+	<email>re at FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://www.FreeBSD.org/releases/11.0R/announce.html">&os; 11.0-RELEASE Announcement</url>
+      <url href="https://www.FreeBSD.org/releases/11.0R/relnotes.html">&os; 11.0-RELEASE Release Notes</url>
+      <url href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; Development Snapshots</url>
+    </links>
+
+    <body>
+      <p>The &os; Release Engineering Team is responsible for setting
+	and publishing release schedules for official project releases
+	of &os;, announcing code freezes, and maintaining the
+	respective branches, among other things.</p>
+
+      <p>The &os; Release Engineering Team in concert with
+	the &os; Security Team finalized &os; 11.0-RELEASE.
+	&os; 11.0-RELEASE was announced on October 10, 2016,
+	roughly four weeks after the original schedule.</p>
+
+      <p>The &os; Release Engineering Team would like to
+	specifically thank &a.cperciva; and all members of the
+	&os; Security Team for their extra diligence in ensuring
+	that user-facing upgrade paths were properly addressed and
+	documented.</p>
+    </body>
+
+    <sponsor>
+	The &os; Foundation
+    </sponsor>
+  </project>
 </report>
