svn commit: r43934 - user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng

[Glen Barber]

Author: gjb
Date: Fri Feb 14 22:31:01 2014
New Revision: 43934
URL: http://svnweb.freebsd.org/changeset/doc/43934

Log:
  Add notes about "blanket approval" requests and work-in-progress
  extensions that are typical after announcing the schedule for a
  release cycle.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml

Modified: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml
==============================================================================
--- user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml	Fri Feb 14 22:30:59 2014	(r43933)
+++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml	Fri Feb 14 22:31:01 2014	(r43934)
@@ -172,6 +172,30 @@
 
     <para>After general agreement on the schedule, the &team.re;
       emails the the schedule to the &os; Developers.</para>
+
+    <para>It is somewhat typical that many developers will inform
+      the &team.re; about various works-in-progress.  In some cases,
+      and extension for the in-progress work will be requested, and
+      in other cases, a request for <quote>blanket approval</quote>
+      to a particular subset of the tree will be made.</para>
+
+    <para>When such requests are made, it is important to make sure
+      timelines (even if estimated) are discussed.  For blanket
+      approvals, the length of time for the blanket approval should
+      be made clear.  For example, a &os; developer may request
+      blanket approvals from the start of the code slush until the
+      start of the <literal>-RC</literal> builds.</para>
+
+    <para>Depending on the underlying set of code in question, and
+      the overall impact the set of code has on &os; as a whole, such
+      requests may be approved or denied by the &team.re;.</para>
+
+    <para>The same applies to work-in-progress extensions.  For
+      example, in-progress work for a new device driver that is
+      otherwise isolated from the rest of the tree may be granted
+      an extension.  A new scheduler, however, may not be feasible,
+      expecially if such dramatic changes do not exist in another
+      branch.</para>
   </sect1>
 
   <sect1 xml:id="releng-head">