From owner-svn-doc-all@freebsd.org Tue Jul 9 20:26:05 2019 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48D3F15E56B2; Tue, 9 Jul 2019 20:26:05 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E37B0854E5; Tue, 9 Jul 2019 20:26:04 +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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B6EDF4DE2; Tue, 9 Jul 2019 20:26:04 +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 x69KQ4Ht051699; Tue, 9 Jul 2019 20:26:04 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x69KQ4s1051698; Tue, 9 Jul 2019 20:26:04 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201907092026.x69KQ4s1051698@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 9 Jul 2019 20:26:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53241 - head/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Commit-Revision: 53241 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: E37B0854E5 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.96)[-0.956,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 09 Jul 2019 20:26:05 -0000 Author: gjb Date: Tue Jul 9 20:26:04 2019 New Revision: 53241 URL: https://svnweb.freebsd.org/changeset/doc/53241 Log: Further clarify what is required for an EN request submission. Submitted by: jhb Sponsored by: Rubicon Communications, LLC (Netgate) Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Tue Jul 9 19:28:21 2019 (r53240) +++ head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Tue Jul 9 20:26:04 2019 (r53241) @@ -464,23 +464,24 @@ To request an Errata Notice after a release cycle has - completed, it is most helpful to fill out the Errata Notice template, in particular the Background, Problem Description, Impact, and if applicable, Workaround sections. + The completed Errata Notice template should be emailed + together with either a patch against the &branch.releng; + branch or a list of revisions against the &branch.stable; + branch. + For Errata Notice requests immediately following the release, the request should be emailed to both &team.re; and &team.secteam;. Once the &branch.releng; branch has been handed over to &team.secteam; as described in , Errata Notice requests - should be sent to &team.secteam;. In either case, the email - should contain at least the patch against the &branch.releng; - branch (and the Errata Notice template, if it had been filled - in), or the revision(s) to be included in the Errata - Notice. + should be sent to &team.secteam;.