From owner-svn-doc-head@freebsd.org Thu Apr 6 19:23:41 2017 Return-Path: Delivered-To: svn-doc-head@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 D1727D323F7; Thu, 6 Apr 2017 19:23:41 +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 AE496163; Thu, 6 Apr 2017 19:23:41 +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 v36JNeiD017376; Thu, 6 Apr 2017 19:23:40 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v36JNehw017374; Thu, 6 Apr 2017 19:23:40 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201704061923.v36JNehw017374@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Thu, 6 Apr 2017 19:23:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50135 - 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-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2017 19:23:41 -0000 Author: gjb Date: Thu Apr 6 19:23:40 2017 New Revision: 50135 URL: https://svnweb.freebsd.org/changeset/doc/50135 Log: Note how blanket approvals and pending requests for approval are tracked internally. Add a note about an internal copy of the CHECKSUM files and the MANIFEST files stored in the misc/freebsd-release-manifests port. Suggested by: marius 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 Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Thu Apr 6 11:25:45 2017 (r50134) +++ head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Thu Apr 6 19:23:40 2017 (r50135) @@ -336,6 +336,26 @@ blanket approvals from the start of the code slush until the start of the RC builds. + + In order to keep track of blanket approvals, the &team.re; + uses an internal repository to keep a running log of such + requests, which defines the area upon which a blanket approval + was granted, the author(s), when the blanket approval expires, + and the reason the approval was granted. One example of this + is granting blanket approval to release/doc/ to all &team.re; + members until the final RC to update the + release notes and other release-related documentation. + + + + The &team.re; also uses this repository to track pending + approval requests that are received just prior to starting + various builds during the release cycle, which the Release + Engineer specifies the cutoff period with an email to the &os; + developers. + + 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;. @@ -399,6 +419,11 @@ &team.secteam; revisit changes that were not approved prior to the final release, and depending on the scope of the change in question, may issue an EN. + + + The actual process of issuing ENs is + handled by the &team.secteam;. + Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Thu Apr 6 11:25:45 2017 (r50134) +++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Thu Apr 6 19:23:40 2017 (r50135) @@ -234,6 +234,17 @@ KERNEL="GENERIC64" to the relevant branch, such as &branch.stablex; or &branch.relengx;. + During the release cycle, a copy of + CHECKSUM.SHA512 and + CHECKSUM.SHA256 for each architecture are + stored in the &team.re; internal repository in addition to being + included in the various announcement emails. Each + MANIFEST containing the hashes of + base.txz, kernel.txz, + etc. are added to + misc/freebsd-release-manifests in the Ports + Collection, as well. + After building the final RELEASE, the &branch.relengx; branch is tagged as &branch.releasex; using the revision from which the RELEASE was built.