From owner-svn-doc-user@freebsd.org Tue Feb 7 18:24:59 2017 Return-Path: Delivered-To: svn-doc-user@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D476CD594E for ; Tue, 7 Feb 2017 18:24:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77D821F79; Tue, 7 Feb 2017 18:24:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v17IOwCU005314; Tue, 7 Feb 2017 18:24:58 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v17IOwpV005313; Tue, 7 Feb 2017 18:24:58 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201702071824.v17IOwpV005313@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 7 Feb 2017 18:24:58 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-user@freebsd.org Subject: svn commit: r49947 - 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.23 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: Tue, 07 Feb 2017 18:24:59 -0000 Author: gjb Date: Tue Feb 7 18:24:58 2017 New Revision: 49947 URL: https://svnweb.freebsd.org/changeset/doc/49947 Log: Use the dates from the original 11.0-RELEASE cycle, and add in missing milestones, such as the Ports and Doc tree tags. Add a section outlining which teams are responsible for some of these milestones. 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 Tue Feb 7 17:42:16 2017 (r49946) +++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml Tue Feb 7 18:24:58 2017 (r49947) @@ -151,58 +151,140 @@ &branch.head; slush: - August 24 + May 27, 2016 &branch.head; freeze: - September 7 + June 10, 2016 &branch.head; KBI freeze: - September 21 + June 24, 2016 + + + + doc/ tree slush [1]: + June 24, 2016 + + + + Ports quarterly branch [2]: + July 1, 2016 &branch.stablex; branch: - October 10 + July 8, 2016 + + + + doc/ tree tag [3]: + July 8, 2016 BETA1 build starts: - October 12 + July 8, 2016 + + + + &branch.head; thaw: + July 9, 2016 BETA2 build starts: - October 18 + July 15, 2016 + + + + BETA3 build starts [*]: + July 22, 2016 &branch.relengx; branch: - November 1 + July 29, 2016 RC1 build starts: - November 1 + July 29, 2016 + + + + &branch.stablex; thaw: + July 30, 2016 RC2 build starts: - November 9 + August 5, 2016 + + + + Final Ports package builds [4]: + August 6, 2016 + + + + Ports release tag: + August 12, 2016 + + + + RC3 build starts [*]: + August 12, 2016 RELEASE build starts: - November 19 + August 19, 2016 + + + + RELEASE announcement: + September 2, 2016 + Items marked with "[*]" are "as + needed". + + + + + The doc/ tree slush is coordinated by + the &team.doceng;. + + + + The Ports quarterly branch used is determined by when + the final RC build is planned. A new + quarterly branch is created on the first day of the quarter, + so this metric should be used when taking the release cycle + milestones into account. The quarterly branch is created by + the &team.portmgr;. + + + + The doc/ tree is tagged by the + &team.doceng;. + + + + The final Ports package build is done by the + &team.portmgr; after the final (or what is expected to be + final) RC build. + + + + If the release is being created from an existing &branch.stable; branch, the KBI freeze date can be excluded, since the KBI