os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add re entry from gjb

Browse source
This commit is contained in:
Benjamin Kaduk 2016-01-12 04:12:47 +00:00
parent 20c6724cc6
commit 1ce3ff9a5e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=47997
1 changed files with 46 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

46
en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml
View file

@ -1828,4 +1828,50 @@
The FreeBSD Foundation
</sponsor>
</project>
<project cat='team'>
<title>&os; Release Engineering Team</title>
<contact>
<person>
<name>&os;&nbsp;Release Engineering Team</name>
<email>re@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://www.freebsd.org/releases/10.3R/schedule.html">&os;&nbsp;10.3-RELEASE schedule</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>During the last quarter of 2015, the Release Engineering team
added support for three additional &os;/arm systems:
<tt>BANANAPI</tt>, <tt>CUBIEBOARD</tt>, and
<tt>CUBIEBOARD2</tt>.</p>
<p>In addition to regular development snapshot builds for
&os;&nbsp;11.0-CURRENT and &os;&nbsp;10.2-STABLE, several
changes and enhancements were made to the release build code.
Of note, the release build code no longer produces MD5
checksums, in favor of SHA512.</p>
<p>Toward the end of the year, much of the primary focus was
centered around the upcoming &os;&nbsp;10.3 release cycle,
which will begin during January 2016.</p>
<p>As always, help testing development snapshot builds is
crucial to producing quality releases, and we encourage
testing development snapshots whenever possible.</p>
</body>
<sponsor>
The FreeBSD Foundation
</sponsor>
</project>
</report>