Add a release engineering section of the web site, with information
about : * Upcoming Release Schedule. * Links to release engineering documentation. * Specific schedule for FreeBSD 4.6. * Current release engineering team. In the very near future, this page will also contain a charter for the RE team, a tentative schedule for 5.0, information about code freezes, etc..
This commit is contained in:
parent
21fa5f06a2
commit
577d56312d
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=12352
2 changed files with 118 additions and 0 deletions
12
en/releng/Makefile
Normal file
12
en/releng/Makefile
Normal file
|
@ -0,0 +1,12 @@
|
|||
# $FreeBSD$
|
||||
|
||||
.if exists(../Makefile.conf)
|
||||
.include "../Makefile.conf"
|
||||
.endif
|
||||
.if exists(../Makefile.inc)
|
||||
.include "../Makefile.inc"
|
||||
.endif
|
||||
|
||||
DOCS?= index.sgml
|
||||
|
||||
.include "${WEB_PREFIX}/share/mk/web.site.mk"
|
106
en/releng/index.sgml
Normal file
106
en/releng/index.sgml
Normal file
|
@ -0,0 +1,106 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD$">
|
||||
<!ENTITY email 're'>
|
||||
<!ENTITY title "Release Engineering Information">
|
||||
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
||||
<!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
|
||||
]>
|
||||
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<p>This page contains documentation about the FreeBSD release
|
||||
engineering process.</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="#schedule">Upcoming Release Schedule</a>.</li>
|
||||
<li>Charter for the Release Engineering Team - <em>Coming Soon</em>.</li>
|
||||
<li><a href="#docs">Release Engineering Documentation</a>.</li>
|
||||
<li><a href="#team">Current Release Engineering Team</a>.</li>
|
||||
<li><a href="&base;/releases/4.6R/schedule.html">FreeBSD 4.6 Release
|
||||
Schedule</a>.</li>
|
||||
<li>FreeBSD 5.0 Release Schedule - <em>Coming Soon</em>.</li>
|
||||
<!--
|
||||
<li>Information about code freezes.</li>
|
||||
<li>General information about committing to -STABLE.</li>
|
||||
-->
|
||||
</ul>
|
||||
|
||||
<a name="schedule"></a>
|
||||
<h1>Upcoming Release Schedule</h1>
|
||||
|
||||
<ul>
|
||||
<li><p><strong>April 1, 2002</strong> : FreeBSD 5.0 Developer
|
||||
Preview 1</p></li>
|
||||
<li><p><strong>June 1, 2002</strong> : <a href="&base;/releases/4.6R/schedule.html">FreeBSD 4.6</a></p></li>
|
||||
<li><p><strong>June 25, 2002</strong> : FreeBSD 5.0 Developer
|
||||
Preview 2</p></li>
|
||||
<li><p><em>[optionally, a third 5.0 DP if necessary]</em></p></li>
|
||||
<li><p><strong>October 1, 2002</strong> : FreeBSD 4.7</p></li>
|
||||
<li><p><strong>November 20, 2002</strong> : FreeBSD 5.0</p></li>
|
||||
<li><p><strong>February 1, 2003</strong> : FreeBSD 4.8</p></li>
|
||||
</ul>
|
||||
|
||||
<a name="docs"></a>
|
||||
<h1>Release Engineering Documentation</h1>
|
||||
|
||||
<ul>
|
||||
<li><p><a
|
||||
href="&base;/doc/en_US.ISO8859-1/articles/releng/index.html">FreeBSD
|
||||
Release Engineering</a><br>
|
||||
|
||||
<small>Describes the approach used by the FreeBSD release
|
||||
engineering team to make production quality releases of the
|
||||
FreeBSD Operating System. It describes the tools available
|
||||
for those interested in producing customized FreeBSD releases
|
||||
for corporate rollouts or commercial
|
||||
productization.</small></p></li>
|
||||
|
||||
|
||||
<li><p><a
|
||||
href="&base;/doc/en_US.ISO8859-1/articles/releng-packages/index.html">FreeBSD
|
||||
Release Engineering for Third Party Packages</a><br>
|
||||
|
||||
<small>Describes the approach used by the FreeBSD release
|
||||
engineering team to produce a high quality package set
|
||||
suitable for official FreeBSD release media. This document is
|
||||
a work in progress, but eventually it will cover the process
|
||||
used to build a clean package set on the FreeBSD.org "Ports
|
||||
Cluster", how to configure any other set of machines as a
|
||||
ports cluster, how to split up the packages for the release
|
||||
media, and how to verify that a package set is
|
||||
consistent.</small></p></li>
|
||||
|
||||
</ul>
|
||||
|
||||
<a name="team"></a>
|
||||
<h1>Release Engineering Team</h1>
|
||||
|
||||
<p>The primary release engineering team is responsible for approving
|
||||
<a
|
||||
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a>
|
||||
requests during code freezes, setting release schedules, and all of
|
||||
the other responsibilities laid out in our charter. <em>(coming
|
||||
soon)</em>.</p>
|
||||
|
||||
<p><strong>Primary RE Team (<a
|
||||
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>)</strong> : &a.murray;
|
||||
is the primary RE / chairperson, and &a.steve;, &a.rwatson;, &a.jhb;,
|
||||
&a.brian;, and &a.bmah; form the rest of the primary release
|
||||
engineering decision-making group.</p>
|
||||
|
||||
<p>The platform-specific release engineering teams are responsible for
|
||||
building and packaging FreeBSD releases on the given platforms.</p>
|
||||
|
||||
<p><strong>Alpha Platform REs (<a
|
||||
href="mailto:re-alpha@FreeBSD.org">re-alpha@FreeBSD.org</a>)</strong> :
|
||||
&a.wilko;, &a.obrien;, &a.murray;, &a.jhb;, &a.rwatson;</p>
|
||||
|
||||
<p><strong>i386 Platform REs (<a
|
||||
href="mailto:re-x86@FreeBSD.org">re-x86@FreeBSD.org</a>)</strong> :
|
||||
&a.murray;, &a.jhb;, &a.rwatson;, &a.bmah;, &a.brian;</p>
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
Loading…
Reference in a new issue