#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2018-12-08 14:45-0200\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Put one translator per line, in the form NAME , YEAR1, YEAR2 msgctxt "_" msgid "translator-credits" msgstr "" #. (itstool) path: info/title #: article.translate.xml:26 msgid "FreeBSD Release Engineering" msgstr "" #. (itstool) path: affiliation/address #: article.translate.xml:37 #, no-wrap msgid "gjb@FreeBSD.org" msgstr "" #. (itstool) path: authorgroup/author #: article.translate.xml:29 msgid "" " Glen Barber The FreeBSD Foundation <_:address-1/> " msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:43 msgid "FreeBSD is a registered trademark of the FreeBSD Foundation." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:45 msgid "" "Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, " "and Xeon are trademarks or registered trademarks of Intel Corporation or its " "subsidiaries in the United States and other countries." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:49 msgid "" "Many of the designations used by manufacturers and sellers to distinguish " "their products are claimed as trademarks. Where those designations appear in " "this document, and the FreeBSD Project was aware of the trademark claim, the " "designations have been followed by the or the ® symbol." msgstr "" #. (itstool) path: info/pubdate #: article.translate.xml:57 msgid "" "$FreeBSD: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml 52377 " "2018-10-18 16:11:27Z gjb $" msgstr "" #. (itstool) path: abstract/para #: article.translate.xml:60 msgid "" "This article describes the release engineering process of the " "FreeBSD Project." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:66 msgid "Introduction to the FreeBSD Release Engineering Process" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:69 msgid "" "Development of FreeBSD has a very specific workflow. In general, all changes " "to the FreeBSD base system are committed to the head/ " "branch, which reflects the top of the source tree." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:74 msgid "" "After a reasonable testing period, changes can then be merged to the " "stable/ branches. The default minimum timeframe before " "merging to stable/ branches is three (3) days." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:79 msgid "" "Although a general rule to wait a minimum of three days before merging from " "head/, there are a few special circumstances where an " "immediate merge may be necessary, such as a critical security fix, or a bug " "fix that directly inhibits the release build process." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:85 msgid "" "After several months, and the number of changes in the stable/ branch have grown significantly, it is time to release the next " "version of FreeBSD. These releases have been historically referred to as " "point releases." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:91 msgid "" "In between releases from the stable/ branches, " "approximately every two (2) years, a release will be cut directly from " "head/. These releases have been historically referred to " "as dot-zero releases." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:97 msgid "" "This article will highlight the workflow and responsibilities of the FreeBSD " "Release Engineering Team for both dot-zero and point' releases." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:102 msgid "The following sections of this article describe:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:109 msgid "General information and preparation before starting the release cycle." msgstr "" #. (itstool) path: listitem/para #. (itstool) path: sect1/title #: article.translate.xml:118 article.translate.xml:508 msgid "Website Changes During the Release Cycle" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:126 msgid "" "Terminology and general information, such as the code slush " "and code freeze, used throughout this document." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:136 msgid "The Release Engineering process for a dot-zero release." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:145 msgid "The Release Engineering process for a point release." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:154 msgid "" "Information related to the specific procedures to build installation medium." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:163 msgid "Procedures to publish installation medium." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:171 msgid "Wrapping up the release cycle." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:178 msgid "General Information and Preparation" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:180 msgid "" "Approximately two months before the start of the release cycle, the FreeBSD " "Release Engineering Team decides on a schedule for the release. The schedule " "includes the various milestone points of the release cycle, such as freeze " "dates, branch dates, and build dates. For example:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:190 msgid "Milestone" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:191 msgid "Anticipated Date" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:197 msgid "head/ slush:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:198 msgid "May 27, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:202 msgid "head/ freeze:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:203 msgid "June 10, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:207 msgid "head/ KBI freeze:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:208 article.translate.xml:213 msgid "June 24, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:212 msgid "doc/ tree slush [1]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:217 msgid "Ports quarterly branch [2]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:218 msgid "July 1, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:222 msgid "stable/12/ branch:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:223 article.translate.xml:228 #: article.translate.xml:233 msgid "July 8, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:227 msgid "doc/ tree tag [3]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:232 msgid "BETA1 build starts:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:237 msgid "head/ thaw:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:238 msgid "July 9, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:242 msgid "BETA2 build starts:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:243 msgid "July 15, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:247 msgid "BETA3 build starts [*]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:248 msgid "July 22, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:252 msgid "releng/12.0/ branch:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:253 article.translate.xml:258 msgid "July 29, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:257 msgid "RC1 build starts:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:262 msgid "stable/12/ thaw:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:263 msgid "July 30, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:267 msgid "RC2 build starts:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:268 msgid "August 5, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:272 msgid "Final Ports package builds [4]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:273 msgid "August 6, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:277 msgid "Ports release tag:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:278 article.translate.xml:283 msgid "August 12, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:282 msgid "RC3 build starts [*]:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:287 msgid "RELEASE build starts:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:288 msgid "August 19, 2016" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:292 msgid "RELEASE announcement:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:293 msgid "September 2, 2016" msgstr "" #. (itstool) path: note/para #: article.translate.xml:300 msgid "Items marked with \"[*]\" are \"as needed\"." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:306 msgid "" "The doc/ tree slush is coordinated by the FreeBSD " "Documentation Engineering Team." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:311 msgid "" "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 " "FreeBSD Ports Management Team." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:320 msgid "" "The doc/ tree is tagged by the FreeBSD Documentation " "Engineering Team." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:325 msgid "" "The final Ports package build is done by the FreeBSD Ports Management Team " "after the final (or what is expected to be final) RC " "build." msgstr "" #. (itstool) path: note/para #: article.translate.xml:332 msgid "" "If the release is being created from an existing stable/ " "branch, the KBI freeze date can be excluded, since the " "KBI is already considered frozen on established " "stable/ branches." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:339 msgid "" "When writing the release cycle schedule, a number of things need to be taken " "into consideration, in particular milestones 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 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." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:349 msgid "" "After general agreement on the schedule, the FreeBSD Release Engineering " "Team emails the schedule to the FreeBSD Developers." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:352 msgid "" "It is somewhat typical that many developers will inform the FreeBSD Release " "Engineering Team about various works-in-progress. In some cases, an " "extension for the in-progress work will be requested, and in other cases, a " "request for blanket approval to a particular subset of the " "tree will be made." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:358 msgid "" "When such requests are made, it is important to make sure timelines (even if " "estimated) are discussed. For blanket approvals, the length of time for the " "blanket approval should be made clear. For example, a FreeBSD developer may " "request blanket approvals from the start of the code slush until the start " "of the RC builds." msgstr "" #. (itstool) path: note/para #: article.translate.xml:366 msgid "" "In order to keep track of blanket approvals, the FreeBSD Release Engineering " "Team 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 FreeBSD Release " "Engineering Team members until the final RC to update the " "release notes and other release-related documentation." msgstr "" #. (itstool) path: note/para #: article.translate.xml:377 msgid "" "The FreeBSD Release Engineering Team 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 FreeBSD developers." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:384 msgid "" "Depending on the underlying set of code in question, and the overall impact " "the set of code has on FreeBSD as a whole, such requests may be approved or " "denied by the FreeBSD Release Engineering Team." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:388 msgid "" "The same applies to work-in-progress extensions. For example, in-progress " "work for a new device driver that is otherwise isolated from the rest of the " "tree may be granted an extension. A new scheduler, however, may not be " "feasible, especially if such dramatic changes do not exist in another branch." "" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:395 msgid "" "The schedule is also added to the Project website, in the doc/ repository, in head/en_US.ISO8859-1/htdocs/releases/" "12.0R/schedule.xml. This file is " "continuously updated as the release cycle progresses." msgstr "" #. (itstool) path: note/para #: article.translate.xml:402 msgid "" "In most cases, the schedule.xml can be copied from a " "prior release and updated accordingly." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:406 msgid "" "In addition to adding schedule.xml to the website, " "head/share/xml/navibar.ent and head/share/xml/" "release.ent are also updated to add the link to the schedule to " "various subpages, as well as enabling the link to the schedule on the " "Project website index page." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:413 msgid "" "The schedule is also linked from head/en_US.ISO8859-1/htdocs/" "releng/index.xml." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:416 msgid "" "Approximately one month prior to the scheduled code slush, " "the FreeBSD Release Engineering Team sends a reminder email to the FreeBSD " "Developers." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:420 msgid "" "Once the first builds of the release cycle are available, update the " "beta.local.where entity in head/en_US.ISO8859-1/" "htdocs/releases/12.0R/schedule.xml. " "replacing IGNORE with INCLUDE." msgstr "" #. (itstool) path: note/para #: article.translate.xml:427 msgid "" "If two parallel release cycles are happening at once, the beta2." "local.where entity may be used instead." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:440 msgid "Release Engineering Terminology" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:442 msgid "" "This section describes some of the terminology used throughout the rest of " "this document." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:446 msgid "The Code Slush" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:448 msgid "" "Although the code slush is not a hard freeze on the tree, the FreeBSD " "Release Engineering Team requests that bugs in the existing code base take " "priority over new features." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:452 msgid "The code slush does not enforce commit approvals to the branch." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:457 msgid "The Code Freeze" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:459 msgid "" "The code freeze marks the point in time where all commits to the branch " "require explicit approval from the FreeBSD Release Engineering Team." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:462 msgid "" "The FreeBSD Subversion repository contains " "several hooks to perform sanity checks before any commit is actually " "committed to the tree. One of these hooks will evaluate if committing to a " "particular branch requires specific approval." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:468 msgid "" "To enforce commit approvals by the FreeBSD Release Engineering Team, the " "Release Engineer updates base/svnadmin/conf/approvers, " "and commits the change back to the repository. Once this is done, any change " "to the branch must include an Approved by: line in the commit " "message." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:475 msgid "" "The Approved by: line must match the second column in " "base/svnadmin/conf/approvers, otherwise the commit will " "be rejected by the repository hooks." msgstr "" #. (itstool) path: note/para #: article.translate.xml:481 msgid "" "During the code freeze, FreeBSD committers are urged to follow the Change Request Guidelines." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:488 msgid "The KBI/KPI Freeze" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:491 msgid "" "KBI/KPI stability implies that the " "caller of a function across two different releases of software that " "implement the function results in the same end state. The caller, whether it " "is a process, thread, or function, expects the function to operate in a " "certain way, otherwise the KBI/KPI " "stability on the branch is broken." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:510 msgid "" "This section describes the changes to the website that should occur as the " "release cycle progresses." msgstr "" #. (itstool) path: note/para #: article.translate.xml:514 msgid "" "The files specified throughout this section are relative to the " "head/ branch of the doc repository in " "Subversion." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:521 msgid "Website Changes Before the Release Cycle Begins" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:523 msgid "" "When the release cycle schedule is available, these files need to be updated " "to enable various different functionalities on the FreeBSD Project website:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:531 article.translate.xml:583 #: article.translate.xml:708 article.translate.xml:787 #: article.translate.xml:896 article.translate.xml:980 msgid "File to Edit" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:532 article.translate.xml:584 #: article.translate.xml:709 article.translate.xml:788 #: article.translate.xml:897 article.translate.xml:981 msgid "What to Change" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:538 article.translate.xml:545 #: article.translate.xml:552 article.translate.xml:559 #: article.translate.xml:597 msgid "share/xml/release.ent" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:539 msgid "" "Change beta.upcoming from IGNORE to " "INCLUDE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:546 msgid "" "Change % beta.upcoming from IGNORE to " "INCLUDE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:553 msgid "" "Change beta.testing from IGNORE to " "INCLUDE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:560 msgid "" "Change % beta.testing from IGNORE to " "INCLUDE" msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:570 msgid "" "Website Changes During BETA or RC" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:573 msgid "" "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:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:590 msgid "" "en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:591 msgid "" "Change % beta.local.where IGNORE to " "INCLUDE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:598 msgid "" "Update % betarel.vers to BETA1" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:603 msgid "share/xml/news.xml" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:604 msgid "Add an entry announcing the BETA" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:611 msgid "" "Once the releng/12.0/ branch " "is created, the various release-related documents need to be generated and " "manually added to the doc/ repository." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:615 msgid "" "Within release/doc, invoke " "make1 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." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:625 msgid "" "The fbsd:nokeywords must be set to on " "on the newly-added files before the pre-commit hooks will allow them to be " "added to the repository." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:632 msgid "" "Ports Changes During BETA, RC, and the " "Final RELEASE" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:636 msgid "" "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 " "bsdinstall8, such as ports-mgmt/poudriere, " "to safely use these distribution sets by providing a mechanism through which " "the checksums can be verified." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:656 msgid "Release from head/" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:659 msgid "" "This section describes the general procedures of the FreeBSD release cycle " "from the head/ branch." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:663 msgid "FreeBSD ALPHA Builds" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:665 msgid "" "Starting with the FreeBSD 10.0-RELEASE cycle, the notion of " "ALPHA builds was introduced. Unlike the " "BETA and RC builds, ALPHA builds are not included in the FreeBSD Release schedule." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:671 msgid "" "The idea behind ALPHA builds is to provide regular " "FreeBSD-provided builds before the creation of the stable/ branch." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:675 msgid "" "FreeBSD ALPHA snapshots should be built approximately " "once a week." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:678 msgid "" "For the first ALPHA build, the BRANCH " "value in sys/conf/newvers.sh needs to be changed from " "CURRENT to ALPHA1. For subsequent " "ALPHA builds, increment each " "ALPHAN value by one." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:686 msgid "" "See for information on building the " "ALPHA images." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:691 msgid "" "Creating the stable/12/ Branch" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:693 msgid "" "When creating the stable/ branch, several changes are " "required in both the new stable/ branch and the " "head/ branch. The files listed are relative to the " "repository root. To create the new stable/12/ branch in Subversion:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:699 #, no-wrap msgid "" "% svn cp ^/head stable/12/" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:701 msgid "" "Once the stable/12/ branch has " "been committed, make the following edits:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:715 msgid "stable/12/UPDATING" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:716 msgid "" "Update the FreeBSD version, and remove the notice about WITNESS" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:721 msgid "" "stable/12/contrib/jemalloc/include/" "jemalloc/jemalloc_FreeBSD.h" msgstr "" #. (itstool) path: entry/screen #: article.translate.xml:722 #, no-wrap msgid "#ifndef MALLOC_PRODUCTION\n" "#define MALLOC_PRODUCTION\n" "#endif" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:728 msgid "" "stable/12/lib/clang/llvm.build.mk" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:729 msgid "Uncomment -DNDEBUG" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:733 msgid "" "stable/12/sys/*/conf/GENERIC*" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:734 article.translate.xml:739 msgid "Remove debugging support" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:738 msgid "" "stable/12/sys/*/conf/MINIMAL" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:743 msgid "" "stable/12/release/release.conf.sample" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:744 msgid "Update SRCBRANCH" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:748 msgid "" "stable/12/sys/*/conf/GENERIC-NODEBUG" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:749 msgid "Remove these kernel configurations" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:753 msgid "" "stable/12/sys/arm/conf/std.arm*" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:754 msgid "Remove debugging options" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:758 article.translate.xml:1013 msgid "" "stable/12/sys/conf/newvers.sh" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:759 msgid "" "Update the BRANCH value to reflect BETA1" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:764 msgid "" "stable/12/libexec/rc/rc.conf" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:765 msgid "" "Set dumpdev from AUTO to NO (it is configurable via bsdinstall8 for those that want it " "enabled by default)" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:772 msgid "" "stable/12/release/Makefile" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:773 msgid "Remove the debug.witness.trace entries" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:780 msgid "" "Then in the head/ branch, which will now become a new " "major version:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:794 msgid "head/UPDATING" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:795 msgid "Update the FreeBSD version" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:799 msgid "head/sys/conf/newvers.sh" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:800 msgid "" "Update the BRANCH value to reflect CURRENT, and increment REVISION" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:806 msgid "head/Makefile.inc1" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:807 msgid "" "Update TARGET_TRIPLE and MACHINE_TRIPLE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:812 msgid "head/sys/sys/param.h" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:813 msgid "Update __FreeBSD_version" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:817 msgid "head/gnu/usr.bin/cc/cc_tools/freebsd-native.h" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:818 msgid "" "Update FBSD_MAJOR and FBSD_CC_VER" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:823 msgid "head/contrib/gcc/config.gcc" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:824 msgid "Append the freebsd<version>.h section" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:830 msgid "head/lib/clang/llvm.build.mk" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:831 msgid "Update the value of OS_VERSION" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:850 msgid "head/lib/clang/freebsd_cc_version.h" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:851 msgid "Update FREEBSD_CC_VERSION" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:856 msgid "head/lib/clang/include/lld/Common/Version.inc" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:857 msgid "Update LLD_REVISION_STRING" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:862 msgid "head/Makefile.libcompat" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:863 msgid "Update LILB32CPUFLAGS" msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:878 msgid "Release from stable/" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:880 msgid "" "This section describes the general procedures of the FreeBSD release cycle " "from an extablished stable/ branch." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:884 msgid "FreeBSD stable Branch Code Slush" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:886 msgid "" "In preparation for the code freeze on a stable branch, " "several files need to be updated to reflect the release cycle is officially " "in progress. These files are all relative to the top-most level of the " "stable branch:" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:903 msgid "sys/conf/newvers.sh" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:904 msgid "" "Update the BRANCH value to reflect PRERELEASE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:909 msgid "Makefile.inc1" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:910 msgid "Update TARGET_TRIPLE" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:916 msgid "" "In the doc repository, also update head/en_US." "ISO8859-1/htdocs/releases/12.0R/Makefile." "hardware, switching the value of _BRANCH to " "BETAX, " "RCX, or RELEASE, respectively." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:926 msgid "FreeBSD BETA Builds" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:928 msgid "" "Following the code slush, the next phase of the release cycle is the code " "freeze. This is the point at which all commits to the stable branch require " "explicit approval from the FreeBSD Release Engineering Team. This is " "enforced by pre-commit hooks in the Subversion repository by editing " "base/svnadmin/conf/approvers to include a regular " "expression matching the stable/12/ branch for the release:" msgstr "" #. (itstool) path: sect2/programlisting #: article.translate.xml:937 #, no-wrap msgid "" "^/stable/12/ re\n" "^/releng/12.0/ re" msgstr "" #. (itstool) path: note/para #: article.translate.xml:941 msgid "" "There are two general exceptions to requiring commit approval during the " "release cycle. The first is any change that needs to be committed by the " "Release Engineer in order to proceed with the day-to-day workflow of the " "release cycle, the other is security fixes that may occur during the release " "cycle." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:949 msgid "" "Once the code freeze is in effect, the next build from the branch is labeled " "BETA1. This is done by updating the BRANCH value in sys/conf/newvers.sh from " "PRERELEASE to BETA1." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:956 msgid "" "Once this is done, the first set of BETA builds are " "started. Subsequent BETA builds do not require updates to " "any files other than sys/conf/newvers.sh, incrementing " "the BETA build number." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:964 msgid "" "Creating the releng/12.0/ " "Branch" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:966 msgid "" "When the first RC (Release Candidate) build is ready to " "begin, the 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 __FreeBSD_version values, " "for example. The paths listed below are relative to the repository root. The " "order of commits and what to change are:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:974 #, no-wrap msgid "" "% svn cp ^/stable/12/ releng/12.0/" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:987 msgid "" "releng/12.0/sys/conf/newvers.sh" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:988 msgid "" "Change BETAX to RC1" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:994 msgid "" "releng/12.0/sys/sys/param.h" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:995 article.translate.xml:1021 msgid "Update __FreeBSD_version" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:999 msgid "" "releng/12.0/etc/pkg/FreeBSD.conf" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1000 article.translate.xml:1007 msgid "" "Replace latest with quarterly as the " "default package repository location" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1006 msgid "" "releng/12.0/release/pkg_repos/release-" "dvd.conf" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1014 msgid "" "Update BETAX with " "PRERELEASE" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1020 msgid "" "stable/12/sys/sys/param.h" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1025 msgid "svnadmin/conf/approvers" msgstr "" #. (itstool) path: row/entry #: article.translate.xml:1026 msgid "" "Add a new approvers line for the releng branch as was done for the stable " "branch" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:1033 #, no-wrap msgid "" "% svn propdel -R svn:mergeinfo releng/" "12.0/\n" "% svn commit releng/12.0/\n" "% svn commit stable/12/" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1037 msgid "" "Now that two new __FreeBSD_version values exist, also " "update head/en_US.ISO8859-1/books/porters-handbook/versions/" "chapter.xml in the Documentation Project repository." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1042 msgid "" "After the first RC build has completed and tested, the " "stable/ branch can be thawed by removing " "(or commenting) the ^/stable/12/ entry in svnadmin/conf/approvers." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1048 msgid "" "Following the availability of the first RC, FreeBSD " "Bugmeister Team should be emailed to add the new FreeBSD -RELEASE to the versions available in the drop-down menu " "shown in the bug tracker." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:1063 msgid "Building FreeBSD Installation Media" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:1065 msgid "" "This section describes the general procedures producing FreeBSD development " "snapshots and releases." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1069 msgid "Release Build Scripts" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1071 msgid "" "This section describes the build scripts used by FreeBSD Release Engineering " "Team to produce development snapshots and releases." msgstr "" #. (itstool) path: sect3/title #: article.translate.xml:1075 msgid "The release.sh Script" msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1077 msgid "" "Prior to FreeBSD 9.0-RELEASE, src/release/Makefile was " "updated to support bsdinstall8, and the src/" "release/generate-release.sh script was introduced as a wrapper to " "automate invoking the release7 targets." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1084 msgid "" "Prior to FreeBSD 9.2-RELEASE, src/release/release.sh " "was introduced, which heavily based on src/release/generate-" "release.sh included support to specify configuration files to " "override various options and environment variables. Support for " "configuration files provided support for cross building each architecture " "for a release by specifying a separate configuration file for each " "invocation." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1094 msgid "" "As a brief example of using src/release/release.sh to " "build a single release in /scratch:" msgstr "" #. (itstool) path: sect3/screen #: article.translate.xml:1098 #, no-wrap msgid "" "# /bin/sh /usr/src/release/release.sh" msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1100 msgid "" "As a brief example of using src/release/release.sh to " "build a single, cross-built release using a different target directory, " "create a custom release.conf containing:" msgstr "" #. (itstool) path: sect3/programlisting #: article.translate.xml:1105 #, no-wrap msgid "" "# release.sh configuration for powerpc/powerpc64\n" "CHROOTDIR=\"/scratch-powerpc64\"\n" "TARGET=\"powerpc\"\n" "TARGET_ARCH=\"powerpc64\"\n" "KERNEL=\"GENERIC64\"" msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1111 msgid "Then invoke src/release/release.sh as:" msgstr "" #. (itstool) path: sect3/screen #: article.translate.xml:1114 #, no-wrap msgid "" "# /bin/sh /usr/src/release/release.sh -c " "$HOME/release.conf" msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1116 msgid "" "See release7 and src/release/release.conf.sample for more details and example usage." msgstr "" #. (itstool) path: sect3/title #: article.translate.xml:1122 msgid "The thermite.sh Wrapper Script" msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1125 msgid "" "In order to make cross building the full set of architectures supported on a " "given branch faster, easier, and reduce human error factors, a wrapper " "script around src/release/release.sh was written to " "iterate through the various combinations of architectures and invoke " "src/release/release.sh using a configuration file " "specific to that architecture." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1133 msgid "" "The wrapper script is called thermite.sh, which is " "available in the FreeBSD Subversion repository at svn://svn.freebsd." "org/base/user/gjb/thermite/, in addition to configuration files " "used to build head/ and stable/12/ development snapshots." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1141 msgid "" "Using thermite.sh is covered in and ." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1143 msgid "" "Each architecture and individual kernel have their own configuration file " "used by release.sh. Each branch has its own " "defaults-X.conf configuration which contains entries " "common throughout each architecture, where overrides or special variables " "are set and/or overridden in the per-build files." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1150 msgid "" "The per-build configuration file naming scheme is in the form of " "${revision}-${TARGET_ARCH}-${KERNCONF}-${type}.conf, " "where the uppercase variables are equivalent to what " "make1 uses in the build system, and lowercase variables are set " "within the configuration files, mapping to the major version of the " "respective branch." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1158 msgid "" "Each branch also has its own builds-X.conf " "configuration, which is used by thermite.sh. The " "thermite.sh script iterates through each ${revision}, " "${TARGET_ARCH}, ${KERNCONF}, and ${type} value, creating a master list of " "what to build. However, a given combination from the list will only be built " "if the respective configuration file exists, which is where the naming " "scheme above is relevant." msgstr "" #. (itstool) path: sect3/para #: article.translate.xml:1169 msgid "There are two paths of file sourcing:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1173 msgid "" "builds-12.conf -> " "main.conf" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1175 msgid "This controls thermite.sh behavior" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1180 msgid "" "12-amd64-" "GENERIC-snap.conf -> defaults-12.conf -> main.conf" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1184 msgid "" "This controls release/release.sh behavior within the " "build chroot8" msgstr "" #. (itstool) path: note/para #: article.translate.xml:1190 msgid "" "The builds-12.conf, " "defaults-12.conf, and " "main.conf configuration files exist to reduce " "repetition between the various per-build files." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1201 msgid "Building FreeBSD Development Snapshots" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1203 msgid "" "The official release build machines have a specific filesystem layout, which " "using ZFS, thermite.sh takes heavy " "advantage of with clones and snapshots, ensuring a pristine build " "environment." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1209 msgid "" "The build scripts reside in /releng/scripts-" "snapshot/scripts or /releng/scripts-" "release/scripts respectively, to avoid collisions between an " "RC build from a releng branch versus a STABLE snapshot from the respective stable branch." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1216 msgid "" "A separate dataset exists for the final build images, /snap/ftp. This directory contains both snapshots " "and releases directories. They are only used if the " "EVERYTHINGISFINE variable is defined in main." "conf." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1223 msgid "" "The EVERYTHINGISFINE variable name was chosen to avoid " "colliding with a variable that might be possibly set in the user " "environment, accidentally enabling the behavior that depends on it being " "defined." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1229 msgid "" "As thermite.sh iterates through the master list of " "combinations and locates the per-build configuration file, a ZFS dataset is created under /releng, such as /releng/12-amd64-GENERIC-" "snap. The src/, ports/, and " "doc/ trees are checked out to separate ZFS datasets, such as /releng/12-src-" "snap, which are then cloned and mounted into the respective build " "datasets. This is done to avoid checking out a given tree more than once." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1241 msgid "" "Assuming these filesystem paths, thermite.sh would be " "invoked as:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:1244 #, no-wrap msgid "" "# cd /releng/scripts-snapshot/scripts\n" "# ./setrev.sh -b stable/" "12/\n" "# ./zfs-setup.sh -c ./builds-12.conf\n" "# ./thermite.sh -c ./builds-12.conf" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1249 msgid "" "Once the builds have completed, additional helper scripts are available to " "generate development snapshot emails which are sent to the freebsd-" "snapshots@freebsd.org mailing list:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:1254 #, no-wrap msgid "" "# cd /releng/scripts-snapshot/scripts\n" "# ./get-checksums.sh -c ./builds-" "12.conf | ./generate-email.pl > snapshot-" "12-mail" msgstr "" #. (itstool) path: note/para #: article.translate.xml:1258 msgid "" "The generated output should be double-checked for correctness, and the email " "itself should be PGP signed, in-line." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1264 msgid "" "These helper scripts only apply to development snapshot builds. " "Announcements during the release cycle (excluding the final release " "announcement) are created from an email template. A sample of the email " "template currently used can be found here." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1273 msgid "Building FreeBSD Releases" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1275 msgid "" "Similar to building FreeBSD development snapshots, thermite.sh would be invoked the same way. The difference between development " "snapshots and release builds, BETA and RC included, is that the chroot8 configuration files " "must be named with release instead of snap as the \"type\", as mentioned above." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1283 msgid "" "In addition, the BUILDTYPE and types " "must be changed from snap to release " "in defaults-12.conf and " "builds-12.conf, respectively." "" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1291 msgid "" "When building BETA, 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 in " "YYYYMMDD format. If the doc/ and " "ports/ trees have been tagged, also set " "PORTBRANCH and DOCBRANCH to the " "relevant tag path in the Subversion repository, replacing HEAD with the last changed revision. Also set releasesrc in builds-12.conf " "to the relevant branch, such as stable/12/ or releng/12.0/." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1307 msgid "" "During the release cycle, a copy of CHECKSUM.SHA512 and " "CHECKSUM.SHA256 for each architecture are stored in the " "FreeBSD Release Engineering Team 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." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1318 msgid "" "After building the final RELEASE, the releng/" "12.0/ branch is tagged as " "release/12.0.0/ using the " "revision from which the RELEASE was built. Similar to " "creating the stable/12/ and " "releng/12.0/ branches, this is " "done with svn cp. From the repository root:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:1325 #, no-wrap msgid "" "% svn cp ^/releng/12.0/@r306420 release/" "12.0.0/\n" "% svn commit release/12.0." "0/" msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:1337 msgid "Publishing FreeBSD Installation Media to Project Mirrors" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:1339 msgid "" "This section describes the procedure to publish FreeBSD development " "snapshots and releases to the Project mirrors." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1343 msgid "Staging FreeBSD Installation Media Images" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1345 msgid "Staging FreeBSD snapshots and releases is a two part process:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1350 msgid "" "Creating the directory structure to match the hierarchy on ftp-" "master" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1353 msgid "" "If EVERYTHINGISFINE is defined in the build configuration " "files, main.conf in the case of the build scripts " "referenced above, this happens automatically in the " "chroot8 after the build is complete, creating the directory structure " "in ${DESTDIR}/R/ftp-stage with a " "path structure matching what is expected on ftp-master. This is equivalent to running the following in the " "chroot8 directly:" msgstr "" #. (itstool) path: listitem/screen #: article.translate.xml:1362 #, no-wrap msgid "" "# make -C /usr/src/release -f Makefile.mirrors " "EVERYTHINGISFINE=1 ftp-stage" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1364 msgid "" "After each architecture is built, thermite.sh will " "rsync the ${DESTDIR}/R/ftp-stage from the build " "chroot8 to /snap/ftp/snapshots or /snap/ftp/releases on " "the build host, respectively." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1373 msgid "" "Copying the files to a staging directory on ftp-master before moving the files into pub/ to begin propagation to the Project mirrors" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:1378 msgid "" "Once all builds have finished, /snap/ftp/" "snapshots, or /snap/ftp/releases for a release, is polled by ftp-master " "using rsync to /" "archive/tmp/snapshots or /archive/" "tmp/releases, respectively." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1387 msgid "" "On ftp-master in the FreeBSD Project " "infrastructure, this step requires root level access, as " "this step must be executed as the archive user." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1397 msgid "Publishing FreeBSD Installation Media" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1399 msgid "" "Once the images are staged in /archive/tmp/, they are ready to be made public by putting them in /archive/pub/FreeBSD. In order to reduce " "propagation time, pax1 is used to create hard " "links from /archive/tmp to " "/archive/pub/FreeBSD." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1406 msgid "" "In order for this to be effective, both /" "archive/tmp and /archive/pub must reside on the same logical filesystem." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1410 msgid "" "There is a caveat, however, where rsync must be " "used after pax1 in order to correct the symbolic links in " "pub/FreeBSD/snapshots/ISO-IMAGES which pax1 will replace with a " "hard link, increasing the propagation time." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1417 msgid "" "As with the staging steps, this requires root level " "access, as this step must be executed as the archive user." "" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1422 msgid "As the archive user:" msgstr "" #. (itstool) path: sect2/screen #: article.translate.xml:1424 #, no-wrap msgid "" "% cd /archive/tmp/snapshots\n" "% pax -r -w -l . /archive/pub/FreeBSD/" "snapshots\n" "% /usr/local/bin/rsync -avH /archive/tmp/" "snapshots/* /archive/pub/FreeBSD/" "snapshots/" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1428 msgid "" "Replace snapshots with releases as appropriate." msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:1435 msgid "Wrapping up the Release Cycle" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:1437 msgid "This section describes general post-release tasks." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1440 msgid "Post-Release Errata Notices" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1442 msgid "" "As the release cycle approaches conclusion, it is common to have several " "EN (Errata Notice) candidates to address issues that were " "discovered late in the cycle. Following the release, the FreeBSD Release " "Engineering Team and the FreeBSD Security Team 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." msgstr "" #. (itstool) path: note/para #: article.translate.xml:1451 msgid "" "The actual process of issuing ENs is handled by the " "FreeBSD Security Team." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:1457 msgid "Handoff to the FreeBSD Security Team" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:1459 msgid "" "Roughly two weeks following the release, the Release Engineer updates " "svnadmin/conf/approvers changing the approver column " "from re to (so|security-officer) for " "the releng/12.0/ branch." msgstr ""