From owner-svn-doc-user@FreeBSD.ORG Fri Feb 14 22:31:01 2014 Return-Path: Delivered-To: svn-doc-user@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4734314; Fri, 14 Feb 2014 22:31:01 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87B0A1D7D; Fri, 14 Feb 2014 22:31:01 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1EMV1RP068964; Fri, 14 Feb 2014 22:31:01 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1EMV1DK068963; Fri, 14 Feb 2014 22:31:01 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201402142231.s1EMV1DK068963@svn.freebsd.org> From: Glen Barber Date: Fri, 14 Feb 2014 22:31:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-user@freebsd.org Subject: svn commit: r43934 - user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Group: doc-user MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-user@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for doc experimental trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 22:31:01 -0000 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 @@ After general agreement on the schedule, the &team.re; emails the the schedule to the &os; Developers. + + 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 blanket approval + to a particular subset of the tree will be made. + + 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 -RC builds. + + 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;. + + 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.