os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Remove updating of index.html file (not there any more)

Browse source 
- Minor pathname fixes
	- Add some basic timing targets for release bits, how/when to
	  warn mirror admins.
	- Add guidelines on what to name ISO's to make them consistent
	  among releases and architectures (differences confuse users).

Reviewed by:	murray
Approved by:	blackend (mentor)
This commit is contained in:
Ken Smith 2003-11-10 00:02:27 +00:00
parent 88cc83ab25
commit f1ee03aa1f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=18781
1 changed files with 26 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
en_US.ISO8859-1/articles/releng/article.sgml
View file

@ -745,14 +745,6 @@
following files must be modified on <hostid>ftp-master</hostid>:</para>
<variablelist>
<varlistentry>
<term><filename>/pub/FreeBSD/index.html</filename></term>
<listitem>
<para>A simple web page that points to the various important
FTP directories for the current FreeBSD release.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>/pub/FreeBSD/releases/<replaceable>arch</replaceable>/<replaceable>X.Y</replaceable>-RELEASE/</filename></term>
<listitem>
@ -762,7 +754,7 @@
</varlistentry>
<varlistentry>
<term><filename>/pub/FreeBSD/ports/<replaceable>arch</replaceable>/packages/packages-<replaceable>X.Y</replaceable>-release/</filename></term>
<term><filename>/pub/FreeBSD/ports/<replaceable>arch</replaceable>/packages-<replaceable>X.Y</replaceable>-release/</filename></term>
<listitem><para>The complete package build for this
release.</para></listitem>
</varlistentry>
@ -776,12 +768,18 @@
<varlistentry>
<term><filename>/pub/FreeBSD/releases/<replaceable>arch</replaceable>/<replaceable>X.Y</replaceable>-RELEASE/packages</filename></term>
<listitem><para>A symlink to
<filename>../../../ports/i386/packages-<replaceable>X.Y</replaceable>-release</filename>.</para></listitem>
<filename>../../../ports/<replaceable>arch</replaceable>/packages-<replaceable>X.Y</replaceable>-release</filename>.</para></listitem>
</varlistentry>
<varlistentry>
<term><filename>/pub/FreeBSD/releases/<replaceable>arch</replaceable>/ISO-IMAGES/<replaceable>X.Y</replaceable>/<replaceable>X.Y</replaceable>-*.iso</filename></term>
<listitem><para>The ISO images.</para></listitem>
<term><filename>/pub/FreeBSD/releases/<replaceable>arch</replaceable>/ISO-IMAGES/<replaceable>X.Y</replaceable>/<replaceable>X.Y</replaceable>-RELEASE-<replaceable>arch</replaceable>-*.iso</filename></term>
<listitem><para>The ISO images. The <quote>*</quote> is
<filename>disc1</filename>, <filename>disc2</filename>, etc.
Only if there is a <filename>disc1</filename> and there is an
alternative first installation CD (for example a
stripped-down install with no windowing system) there may
be a <filename>mini</filename> as well.</para>
</listitem>
</varlistentry>
</variablelist>
@ -789,11 +787,23 @@
architecture of the FreeBSD FTP sites, please see the <ulink
url="../hubs/">Mirroring FreeBSD</ulink> article.</para>
<para>It may take many hours after updating
<para>It may take many hours to two days after updating
<hostid>ftp-master</hostid> before a majority of the Tier-1 FTP
sites have the new software. It is imperative that the release
engineers coordinate with the &a.hubs; before announcing the general
availability of new software on the FTP sites.</para>
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 &a.mirror-announce; before announcing the general
availability of new software on the FTP sites. Ideally
the release package set should be loaded at least four
days prior to release day. The release bits should be
loaded between 24 and 48 hours before the planned release
time with <quote>other</quote> file permissions turned off.
This will allow the mirror sites to download it but the
general public will not be able to download it from the mirror
sites. Mail should be sent to &a.mirror-announce; at the time
the release bits get posted saying the release has been staged
and giving the time that the mirror sites should begin allowing
access. Be sure to include a time zone with the
time, for example make it relative to GMT.</para>
</sect2>
<sect2 id="dist-cdrom">