svn commit: r43297 - user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng
Glen Barber
gjb at FreeBSD.org
Sun Dec 8 08:02:52 UTC 2013
Author: gjb
Date: Sun Dec 8 08:02:51 2013
New Revision: 43297
URL: http://svnweb.freebsd.org/changeset/doc/43297
Log:
Add work-in-progress release engineering docs.
Sponsored by: The FreeBSD Foundation
Added:
user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/Makefile (contents, props changed)
user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml (contents, props changed)
user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/extra.css (contents, props changed)
Added: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/Makefile
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/Makefile Sun Dec 8 08:02:51 2013 (r43297)
@@ -0,0 +1,21 @@
+#
+# $FreeBSD$
+#
+# Article: FreeBSD Release Engineering
+
+DOC?= article
+
+FORMATS?= html
+WITH_ARTICLE_TOC?= YES
+
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+SRCS= article.xml
+
+CSS_SHEET_ADDITIONS= extra.css
+
+URL_RELPREFIX?= ../../../..
+DOC_PREFIX?= ${.CURDIR}/../../..
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
Added: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml Sun Dec 8 08:02:51 2013 (r43297)
@@ -0,0 +1,189 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
+
+<!-- local entities -->
+<!ENTITY team.re "&os; Release Engineering Team">
+<!ENTITY team.secteam "&os; Security Team">
+<!ENTITY team.portmgr "&os; Ports Management Team">
+<!ENTITY team.doceng "&os; Documentation Engineering Team">
+]>
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+
+ <info><title>&os; Release Engineering</title>
+
+ <legalnotice xml:id="trademarks" role="trademarks">
+ &tm-attrib.freebsd;
+ &tm-attrib.intel;
+ &tm-attrib.general;
+ </legalnotice>
+
+ <pubdate>$FreeBSD$</pubdate>
+
+ <abstract>
+ <para>This article describes the release engineering process of
+ the &os; Project.</para>
+ </abstract>
+ </info>
+
+ <sect1 xml:id="introduction">
+ <title>Introduction to the &os; Release Engineering
+ Process</title>
+
+ <para>Development of &os; has a very specific workflow. In
+ general, all changes to the &os; base system are committed to
+ the <literal>head/</literal> branch, which reflects the top of
+ the source tree.</para>
+
+ <para>After a reasonable testing period, changes can then be
+ merged to the <literal>stable/</literal> branches. The default
+ minimum timeframe before merging to <literal>stable/</literal>
+ branches is three (3) days.</para>
+
+ <para>Although a general rule to wait a minimum of three days
+ before mergeing from <literal>head/</literal>, there are a few
+ special circumstances where an immediate merge may be necessary,
+ such as a critical security fix, or a bug fix that directly
+ inhibits the release build process.</para>
+
+ <para>After several months, and the number of changes in the
+ <literal>stable/</literal> branch have grown significantly, it
+ is time to release the next version of &os;. These releases
+ have been historically referred to as <quote>point</quote>
+ releases.</para>
+
+ <para>In between releases from the <literal>stable/</literal>
+ branches, approximately every two (2) years, a release will be
+ cut directly from <literal>head/</literal>. These releases
+ have been historically referred to as <quote>dot-zero</quote>
+ releases.</para>
+
+ <para>This article will highlight the workflow and
+ responsibilities of the &team.re; for both
+ <quote>dot-zero</quote> and <quote>point</quote>'
+ releases.</para>
+
+ <para>The following sections of this article describe:</para>
+
+ <variablelist>
+ <varlistentry>
+ <term><xref linkend="releng-prep"/></term>
+
+ <listitem>
+ <para>General information and preparation before
+ starting the release cycle.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><xref linkend="releng-head"/></term>
+
+ <listitem>
+ <para>The Release Engineering process for a
+ <quote>dot-zero</quote> release.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><xref linkend="releng-stable"/></term>
+
+ <listitem>
+ <para>The Release Engineering process for a
+ <quote>point</quote> release.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+
+ <sect1 xml:id="releng-prep">
+ <title>General Information and Preparation</title>
+
+ <para>Approximately two months before the start of the release
+ cycle, the &team.re; decides on a schedule for the release.
+ The schedule includes the various milestone points of the
+ release cycle, such as freeze dates, branch dates, and build
+ dates. For example:</para>
+
+ <informaltable frame="none" pgwide="0">
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Milestone</entry>
+ <entry>Anticipated Date</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry><literal>head/</literal> slush:</entry>
+ <entry>August 24</entry>
+ </row>
+
+ <row>
+ <entry><literal>head/</literal> freeze:</entry>
+ <entry>September 7</entry>
+ </row>
+
+ <row>
+ <entry><literal>head/</literal> KBI freeze:</entry>
+ <entry>September 21</entry>
+ </row>
+
+ <row>
+ <entry><literal>stable/<replaceable>10</replaceable>/</literal>
+ branch:</entry>
+ <entry>October 10</entry>
+ </row>
+
+ <row>
+ <entry>BETA1 build starts:</entry>
+ <entry>October 12</entry>
+ </row>
+
+ <row>
+ <entry>BETA2 build starts:</entry>
+ <entry>October 18</entry>
+ </row>
+
+ <row>
+ <entry><literal>releng/<replaceable>10.0</replaceable>/</literal>
+ branch:</entry>
+ <entry>November 1</entry>
+ </row>
+
+ <row>
+ <entry>RC1 build starts:</entry>
+ <entry>November 1</entry>
+ </row>
+
+ <row>
+ <entry>RC2 build starts:</entry>
+ <entry>November 9</entry>
+ </row>
+
+ <row>
+ <entry>RELEASE build starts:</entry>
+ <entry>November 19</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ <para>After general agreement on the schedule, the &team.re;
+ emails the the schedule to the &os; Developers.</para>
+ </sect1>
+
+ <sect1 xml:id="releng-head">
+ <title>Release from <literal>head/</literal></title>
+
+ <para> </para>
+
+ </sect1>
+
+ <sect1 xml:id="releng-stable">
+ <title>Release from <literal>stable/</literal></title>
+
+ <para> </para>
+
+ </sect1>
+</article>
Added: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/extra.css
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/extra.css Sun Dec 8 08:02:51 2013 (r43297)
@@ -0,0 +1,7 @@
+/*
+ * $FreeBSD$
+ */
+
+DIV.TITLEPAGE {
+ text-align: center;
+}
More information about the svn-doc-user
mailing list