From owner-svn-doc-all@freebsd.org Thu Apr 13 16:19:00 2017 Return-Path: Delivered-To: svn-doc-all@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 88666D3CFB4; Thu, 13 Apr 2017 16:19:00 +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 4B80AAE0; Thu, 13 Apr 2017 16:19:00 +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 v3DGIxxf016782; Thu, 13 Apr 2017 16:18:59 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v3DGIxpg016779; Thu, 13 Apr 2017 16:18:59 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201704131618.v3DGIxpg016779@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Thu, 13 Apr 2017 16:18:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50157 - head/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2017 16:19:00 -0000 Author: gjb Date: Thu Apr 13 16:18:59 2017 New Revision: 50157 URL: https://svnweb.freebsd.org/changeset/doc/50157 Log: Use tags around 'RC' references as opposed to the tag, which renders differently. Given how some of this article is written, there are visible differences in the rendered output that may seem confusing. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Wed Apr 12 10:09:36 2017 (r50156) +++ head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Thu Apr 13 16:18:59 2017 (r50157) @@ -283,7 +283,7 @@ The Ports quarterly branch used is determined by when - the final RC build is planned. A new + 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 @@ -298,7 +298,7 @@ The final Ports package build is done by the &team.portmgr; after the final (or what is expected to be - final) RC build. + final) RC build. @@ -315,7 +315,7 @@ where the target date depends on predefined milestones upon which there is a dependency. For example, the Ports Collection release tag originates from the active quarterly branch at the - time of the last RC. This in part defines + time of the last RC. This in part defines which quarterly branch is used, when the release tag can happen, and what revision of the ports tree is used for the final RELEASE build. @@ -334,7 +334,7 @@ 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. + start of the RC builds. In order to keep track of blanket approvals, the &team.re; Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Wed Apr 12 10:09:36 2017 (r50156) +++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Thu Apr 13 16:18:59 2017 (r50157) @@ -159,7 +159,7 @@ KERNEL="GENERIC64" or /releng/scripts-release/scripts respectfully, to avoid collisions between an - RC build from a releng branch versus + RC build from a releng branch versus a STABLE snapshot from the respective stable branch. @@ -205,7 +205,7 @@ KERNEL="GENERIC64" Similar to building &os; development snapshots, thermite.sh would be invoked the same way. The difference between development snapshots and release builds, - BETA and RC, included, is + BETA and RC, included, is that the &man.chroot.8; configuration files must be named with release instead of snap as the "type", as mentioned above. @@ -219,7 +219,7 @@ KERNEL="GENERIC64" respectively. When building BETA, - RC, and the final RELEASE, + RC, and the final RELEASE, also statically set BUILDSVNREV to the revision on the branch reflecting the name change, BUILDDATE to the date the builds are started Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml Wed Apr 12 10:09:36 2017 (r50156) +++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml Thu Apr 13 16:18:59 2017 (r50157) @@ -89,7 +89,7 @@ Creating the &branch.relengx; Branch - When the first RC (Release Candidate) + When the first RC (Release Candidate) build is ready to begin, the &branch.releng; branch is created. This is a multi-step process that must be done in a specific order, in order to avoid anomalies such as overlaps with @@ -165,7 +165,7 @@ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml in the Documentation Project repository. - After the first RC build has completed + After the first RC build has completed and tested, the &branch.stable; branch can be thawed by removing (or commenting) the ^/&branch.stablex; entry in