From owner-svn-doc-head@FreeBSD.ORG Sat Apr 11 04:44:59 2015 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F371485; Sat, 11 Apr 2015 04:44:59 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 78E83ADF; Sat, 11 Apr 2015 04:44:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t3B4ixDJ068122; Sat, 11 Apr 2015 04:44:59 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t3B4ix7j068121; Sat, 11 Apr 2015 04:44:59 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201504110444.t3B4ix7j068121@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Sat, 11 Apr 2015 04:44:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46515 - head/en_US.ISO8859-1/articles/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.18-1 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: Sat, 11 Apr 2015 04:44:59 -0000 Author: gjb Date: Sat Apr 11 04:44:58 2015 New Revision: 46515 URL: https://svnweb.freebsd.org/changeset/doc/46515 Log: Revert r46484, r46485, r46511, r46512: The claim that there were no "substantive" commits to this article are made without any knowledge of internals of re@. Several parts of the removed content is still relevant for 8.x, which we do still support. Furthermore, this particular article, outdated or not, falls under RE territory, and these drive-by commits were not approved. Approved by: re (implicit) Modified: head/en_US.ISO8859-1/articles/releng/article.xml Modified: head/en_US.ISO8859-1/articles/releng/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/releng/article.xml Fri Apr 10 15:54:36 2015 (r46514) +++ head/en_US.ISO8859-1/articles/releng/article.xml Sat Apr 11 04:44:58 2015 (r46515) @@ -5,6 +5,14 @@
&os; Release Engineering + + + + + November 2001 + BSDCon Europe + + MurrayStokely I've been involved in the development of &os; based products @@ -55,7 +63,12 @@ The development of &os; is a very open process. &os; is comprised of contributions from thousands of people around the world. The &os; Project provides - Subversion + Subversion + + + Subversion, http://subversion.apache.org + + access to the general public so that others can have access to log messages, diffs (patches) between development branches, and other productivity enhancements that @@ -66,8 +79,18 @@ Therefore only a select group of nearly 300 people are given write access to the Subversion repository. These committers + + + FreeBSD committers + + are usually the people who do the bulk of &os; development. An elected Core Team + + + &os; Core Team + + of developers provide some level of direction over the project. The rapid pace of &os; @@ -145,6 +168,55 @@ available to keep systems on the releng/X.Y branches updated. + + + What this article describes + + The following sections of this article describe: + + + + + + + The different phases of the release engineering process + leading up to the actual system build. + + + + + + + + The actual build process. + + + + + + + + How the base release may be extended by third parties. + + + + + + + + Some of the lessons learned through the release of &os; 4.4. + + + + + + + + Future directions of development. + + + + @@ -446,6 +518,18 @@ + Sysinstall should be updated to note + the number of available ports and the amount of disk space required + for the Ports Collection. + + + &os; Ports Collection + http://www.FreeBSD.org/ports + + + This information is currently kept in + src/usr.sbin/sysinstall/dist.c. + After the release has been built, a number of files should be updated to announce the release to the world. These files are relative to head/ within the @@ -631,6 +715,95 @@ be unwise to distribute binaries that were built on a system with CPUTYPE set to a specific processor. + + + + + Contributed Software (<quote>ports</quote>) + + The &os; Ports + collection is a collection of over &os.numports; + third-party software packages available for &os;. The &a.portmgr; + is responsible for maintaining a consistent ports tree that can be used + to create the binary packages that accompany official &os; + releases. + + + + Release ISOs + + Starting with &os; 4.4, the &os; Project decided to + release all four ISO images that were previously sold on the + BSDi/Wind River Systems/FreeBSD Mall + official CDROM distributions. Each of the four + discs must contain a README.TXT file that + explains the contents of the disc, a + CDROM.INF file that provides meta-data for + the disc so that &man.sysinstall.8; can validate and use the + contents, and a filename.txt file that + provides a manifest for the disc. This + manifest can be created with a simple + command: + + /stage/cdrom&prompt.root; find . -type f | sed -e 's/^\.\///' | sort > filename.txt + + The specific requirements of each CD are outlined below. + + + Disc 1 + + The first disc is almost completely created by + make + release. The only changes + that should be made to the disc1 directory are the addition of + a tools directory, and as many popular + third party software packages as will fit on the disc. The + tools directory contains software that allow users to create + installation floppies from other operating systems. This disc + should be made bootable so that users of modern PCs do not + need to create installation floppy disks. + + If a custom kernel of &os; is to be included, then + &man.sysinstall.8; and &man.release.7; must be updated to + include installation instructions. The relevant code is contained + in src/release and src/usr.sbin/sysinstall. + Specifically, the file src/release/Makefile, and + dist.c, dist.h, + menus.c, install.c, and + Makefile will need to be updated under + src/usr.sbin/sysinstall. Optionally, you may choose + to update sysinstall.8. + + + + + Disc 2 + + The second disc is also largely created by make + release. This disc contains a live + filesystem that can be used from &man.sysinstall.8; to + troubleshoot a &os; installation. This disc should be + bootable and should also contain a compressed copy of the CVS + repository in the CVSROOT directory and + commercial software demos in the commerce + directory. + + + + Multi-volume support + + Sysinstall supports multiple + volume package installations. This requires that each disc + have an INDEX file containing all of the + packages on all volumes of a set, along with an extra field + that indicates which volume that particular package is on. + Each volume in the set must also have the + CD_VOLUME variable set in the + cdrom.inf file so that sysinstall can + tell which volume is which. When a user attempts to install a + package that is not on the current disc, sysinstall will + prompt the user to insert the appropriate one. + @@ -709,6 +882,13 @@ time, for example make it relative to GMT. + + CD-ROM Replication + + Coming soon: Tips for sending &os; ISOs to a replicator + and quality assurance measures to be taken. + + @@ -727,8 +907,25 @@ certainly encourage innovation in the form of advanced installation and administration tools, for example, but we cannot be expected to answer questions about it. + + + Scripting <command>sysinstall</command> + + The &os; system installation and configuration tool, + &man.sysinstall.8;, can be scripted to provide automated installs + for large sites. This functionality can be used in conjunction + with &intel; PXE + + + &url.books.handbook;/network-pxe-nfs.html + + + to bootstrap systems from the network. + + + Lessons Learned from &os; 4.4 @@ -771,12 +968,33 @@ using multiple processors in speeding up the make release process. If multiple disks are used for different hierarchies in the &man.chroot.2; - environment, then the subversion checkout of the ports and doc trees + environment, then the CVS checkout of the ports and doc trees can be happening simultaneously as the make world on another disk. Using a RAID solution (hardware or software) can significantly decrease the overall build time. + + + Cross-building releases - Building + IA-64 or Alpha release on x86 hardware? make + TARGET=ia64 release. + + + + + Regression Testing - We need better + automated correctness testing for &os;. + + + + Installation Tools - Our installation + program has long since outlived its intended life span. + Several projects are under development to provide a more + advanced installation mechanism. The libh project was one + such project that aimed to provide an intelligent new package + framework and GUI installation program. +