Index: head/en_US.ISO8859-1/articles/freebsd-releng/releng-website.xml =================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/releng-website.xml (revision 53595) +++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-website.xml (revision 53596) @@ -1,163 +1,169 @@ Website Changes During the Release Cycle This section describes the changes to the website that should occur as the release cycle progresses. The files specified throughout this section are relative to the head/ branch of the doc repository in Subversion. Website Changes Before the Release Cycle Begins When the release cycle schedule is available, these files need to be updated to enable various different functionalities on the &os; Project website: File to Edit What to Change share/xml/release.ent Change beta.upcoming from IGNORE to INCLUDE share/xml/release.ent Change % beta.upcoming from IGNORE to INCLUDE share/xml/release.ent Change beta.testing from IGNORE to INCLUDE share/xml/release.ent Change % beta.testing from IGNORE to INCLUDE Website Changes During <literal>BETA</literal> or <literal>RC</literal> When transitioning from PRERELEASE to BETA, these files need to be updated to enable the "Help Test" block on the download page. All files are relative to head/ in the doc repository: File to Edit What to Change en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Change % beta.local.where IGNORE to INCLUDE share/xml/release.ent Update % betarel.vers to BETA1 share/xml/news.xml Add an entry announcing the BETA en_US.ISO8859-1/htdocs/security/advisory-template.txt Add the new BETA, RC, or final RELEASE to the template en_US.ISO8859-1/htdocs/security/errata-template.txt Add the new BETA, RC, or final RELEASE to the template Once the &branch.relengx; branch is created, the various release-related documents need to be generated and manually added to the doc/ repository. Within release/doc, invoke &man.make.1; to generate errata.html, hardware.html, readme.html, and relnotes.html pages, which are then added to doc/head/en_US.ISO8859-1/htdocs/releases/X.YR/, where X.Y represents the major and minor version number of the release. - The fbsd:nokeywords must be set to - on on the newly-added files before the + The fbsd:nokeywords property must be set + to on on the newly-added files before the pre-commit hooks will allow them to be added to the repository. + + + The relevant release-related documents exist in the + doc repository for + &os; 12.x and later. + Ports Changes During <literal>BETA</literal>, <literal>RC</literal>, and the Final <literal>RELEASE</literal> For each build during the release cycle, the MANIFEST files containing the SHA256 of the various distribution sets, such as base.txz, kernel.txz, and so on, are added to the misc/freebsd-release-manifests port. This allows utilities other than &man.bsdinstall.8;, such as ports-mgmt/poudriere, to safely use these distribution sets by providing a mechanism through which the checksums can be verified.