Page MenuHomeFreeBSD
Differential D31926 Diff 97856 documentation/content/en/articles/releng/_index.adoc

Changeset View

Standalone View

View Options

documentation/content/en/articles/releng/_index.adoc

Context not available.
:sectnumlevels: 6 :sectnumlevels: 6
:source-highlighter: rouge :source-highlighter: rouge
:experimental: :experimental:
:xrefstyle: full :images-path: articles/releng/
ifdef::env-beastie[]
ifeval::["{backend}" == "html5"] ifdef::backend-html5[]
include::shared/releases.adoc[]
include::shared/authors.adoc[] include::shared/authors.adoc[]
include::shared/en/teams.adoc[lines=16..-1] include::shared/mirrors.adoc[]
include::shared/en/mailing-lists.adoc[] include::shared/releases.adoc[]
include::shared/en/urls.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[]
:imagesdir: ../../../images/articles/releng/ include::shared/{{% lang %}}/teams.adoc[]
include::shared/{{% lang %}}/mailing-lists.adoc[]
include::shared/{{% lang %}}/urls.adoc[]
:imagesdir: ../../../images/{images-path}
endif::[]
ifdef::backend-pdf,backend-epub3[]
include::../../../../shared/asciidoctor.adoc[]
endif::[] endif::[]
ifeval::["{backend}" == "pdf"]
include::../../../../shared/releases.adoc[]
include::../../../../shared/authors.adoc[]
include::../../../../shared/en/teams.adoc[lines=16..-1]
include::../../../../shared/en/mailing-lists.adoc[]
include::../../../../shared/en/urls.adoc[]
:imagesdir: ../../../../static/images/articles/releng/
endif::[] endif::[]
ifeval::["{backend}" == "epub3"] ifndef::env-beastie[]
include::shared/releases.adoc[] include::../../../../../shared/asciidoctor.adoc[]
include::shared/authors.adoc[]
include::shared/en/teams.adoc[lines=16..-1]
include::shared/en/mailing-lists.adoc[]
include::shared/en/urls.adoc[]
:imagesdir: ../../../../static/images/articles/releng/
endif::[] endif::[]
[.abstract-title] [.abstract-title]
Context not available.
==== ====
This document is outdated and does not accurately describe the current release procedures of the FreeBSD Release Engineering team. This document is outdated and does not accurately describe the current release procedures of the FreeBSD Release Engineering team.
It is retained for historical purposes. It is retained for historical purposes.
The current procedures used by the FreeBSD Release Engineering team are available in the link:{freebsd-releng}[FreeBSD Release Engineering] article. The current procedures used by the FreeBSD Release Engineering team are available in the extref:{freebsd-releng}[FreeBSD Release Engineering] article.
==== ====
This paper describes the approach used by the FreeBSD release engineering team to make production quality releases of the FreeBSD Operating System. This paper describes the approach used by the FreeBSD release engineering team to make production quality releases of the FreeBSD Operating System.
Context not available.
This has been a huge help in attracting more talented developers to FreeBSD. This has been a huge help in attracting more talented developers to FreeBSD.
However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet. However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet.
Therefore only a "select" group of nearly 300 people are given write access to the Subversion repository. Therefore only a "select" group of nearly 300 people are given write access to the Subversion repository.
These link:{contributors}#staff-committers[FreeBSD committers]footnote:[link:{contributors}#staff-committers[FreeBSD committers]] are usually the people who do the bulk of FreeBSD development. These extref:{contributors}[FreeBSD committers, staff-committers]footnote:[extref:{contributors}[FreeBSD committers, staff-committers]] are usually the people who do the bulk of FreeBSD development.
An elected link:https://www.FreeBSD.org/administration/#t-core[Core Team]footnote:[link:https://www.FreeBSD.org/administration/#t-core[FreeBSD Core Team]] of developers provide some level of direction over the project. An elected link:https://www.FreeBSD.org/administration/#t-core[Core Team]footnote:[link:https://www.FreeBSD.org/administration/#t-core[FreeBSD Core Team]] of developers provide some level of direction over the project.
The rapid pace of `FreeBSD` development makes the main development branch unsuitable for the everyday use by the general public. The rapid pace of `FreeBSD` development makes the main development branch unsuitable for the everyday use by the general public.
Context not available.
In most cases, binaries from the older _STABLE_ systems run unmodified on newer systems, including __HEAD__, assuming that the system management interfaces are not used. In most cases, binaries from the older _STABLE_ systems run unmodified on newer systems, including __HEAD__, assuming that the system management interfaces are not used.
In the interim period between releases, weekly snapshots are built automatically by the FreeBSD Project build machines and made available for download from `ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/`. In the interim period between releases, weekly snapshots are built automatically by the FreeBSD Project build machines and made available for download from `ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/`.
The widespread availability of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with Subversion and "`make buildworld`" footnote:[link:{handbook}#makeworld[Rebuilding world]] helps to keep FreeBSD-STABLE in a very reliable condition even before the quality assurance activities ramp up pending a major release. The widespread availability of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with Subversion and "`make buildworld`" footnote:[extref:{handbook}[Rebuilding world, makeworld]] helps to keep FreeBSD-STABLE in a very reliable condition even before the quality assurance activities ramp up pending a major release.
In addition to installation ISO snapshots, weekly virtual machine images are also provided for use with VirtualBox, qemu, or other popular emulation software. In addition to installation ISO snapshots, weekly virtual machine images are also provided for use with VirtualBox, qemu, or other popular emulation software.
The virtual machine images can be downloaded from `ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/`. The virtual machine images can be downloaded from `ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/`.
Context not available.
In all examples below, `$FSVN` refers to the location of the FreeBSD Subversion repository, `svn+ssh://svn.FreeBSD.org/base/`. In all examples below, `$FSVN` refers to the location of the FreeBSD Subversion repository, `svn+ssh://svn.FreeBSD.org/base/`.
==== ====
The layout of FreeBSD branches in Subversion is described in the link:{committers-guide}#subversion-primer-base-layout[Committer's Guide]. The layout of FreeBSD branches in Subversion is described in the extref:{committers-guide}[Committer's Guide, subversion-primer-base-layout].
The first step in creating a branch is to identify the revision of the `stable/_X_` sources that you want to branch _from_. The first step in creating a branch is to identify the revision of the `stable/_X_` sources that you want to branch _from_.
[source,shell] [source,shell]
Context not available.
== Release Building == Release Building
FreeBSD "releases" can be built by anyone with a fast machine and access to a source repository. FreeBSD "releases" can be built by anyone with a fast machine and access to a source repository.
(That should be everyone, since we offer Subversion access! See the link:{handbook}#svn[Subversion section in the Handbook] for details.) (That should be everyone, since we offer Subversion access! See the extref:{handbook}[Subversion section in the Handbook, svn] for details.)
The _only_ special requirement is that the man:md[4] device must be available. The _only_ special requirement is that the man:md[4] device must be available.
If the device is not loaded into your kernel, then the kernel module should be automatically loaded when man:mdconfig[8] is executed during the boot media creation phase. If the device is not loaded into your kernel, then the kernel module should be automatically loaded when man:mdconfig[8] is executed during the boot media creation phase.
All of the tools necessary to build a release are available from the Subversion repository in [.filename]#src/release#. All of the tools necessary to build a release are available from the Subversion repository in [.filename]#src/release#.
Context not available.
The ISO images. The "*" is [.filename]#disc1#, [.filename]#disc2#, etc. The ISO images. The "*" is [.filename]#disc1#, [.filename]#disc2#, etc.
Only if there is a [.filename]#disc1# and there is an alternative first installation CD (for example a stripped-down install with no windowing system) there may be a [.filename]#mini# as well. Only if there is a [.filename]#disc1# and there is an alternative first installation CD (for example a stripped-down install with no windowing system) there may be a [.filename]#mini# as well.
For more information about the distribution mirror architecture of the FreeBSD FTP sites, please see the link:{hubs}[Mirroring FreeBSD] article. For more information about the distribution mirror architecture of the FreeBSD FTP sites, please see the extref:{hubs}[Mirroring FreeBSD] article.
It may take many hours to two days after updating `ftp-master` before a majority of the Tier-1 FTP sites have the new software depending on whether or not a package set got loaded at the same time. It may take many hours to two days after updating `ftp-master` before a majority of the Tier-1 FTP sites have the new software depending on whether or not a package set got loaded at the same time.
It is imperative that the release engineers coordinate with the {mirror-announce} before announcing the general availability of new software on the FTP sites. It is imperative that the release engineers coordinate with the {mirror-announce} before announcing the general availability of new software on the FTP sites.
Context not available.
=== Scripting `bsdinstall` === Scripting `bsdinstall`
The FreeBSD system installation and configuration tool, man:bsdinstall[8], can be scripted to provide automated installs for large sites. The FreeBSD system installation and configuration tool, man:bsdinstall[8], can be scripted to provide automated installs for large sites.
This functionality can be used in conjunction with Intel(R) PXE footnote:[link:{handbook}#network-diskless[Diskless Operation with PXE]] to bootstrap systems from the network. This functionality can be used in conjunction with Intel(R) PXE footnote:[extref:{handbook}[Diskless Operation with PXE, network-diskless]] to bootstrap systems from the network.
[[lessons-learned]] [[lessons-learned]]
== Lessons Learned from FreeBSD 4.4 == Lessons Learned from FreeBSD 4.4
Context not available.