You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by je...@apache.org on 2001/11/24 08:15:55 UTC
cvs commit: httpd-site/docs/dev devnotes.html fetch-from-cvs.txt how-to-release.html index.html
jerenkrantz 01/11/23 23:15:55
Modified: docs/dev devnotes.html fetch-from-cvs.txt
how-to-release.html index.html
Log:
Transformation update.
Revision Changes Path
1.3 +1 -1 httpd-site/docs/dev/devnotes.html
Index: devnotes.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/dev/devnotes.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- devnotes.html 2001/11/22 05:02:32 1.2
+++ devnotes.html 2001/11/24 07:15:54 1.3
@@ -250,7 +250,7 @@
</td></tr>
<tr><td>
<blockquote>
-<p>Like the <samp>site</samp> module, this one is used ot
+<p>Like the <samp>site</samp> module, this one is used to
maintain the files that comprise a website - in this case,
<samp>http://httpd.apache.org/</samp>. Also like the previous module,
the directory on the server is a checked-out working copy of this
1.2 +1 -1 httpd-site/docs/dev/fetch-from-cvs.txt
Index: fetch-from-cvs.txt
===================================================================
RCS file: /home/cvs/httpd-site/docs/dev/fetch-from-cvs.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fetch-from-cvs.txt 2001/11/21 07:31:46 1.1
+++ fetch-from-cvs.txt 2001/11/24 07:15:54 1.2
@@ -14,7 +14,7 @@
my $ver = '1.3';
my $dir = shift || "/tmp/apache_$ver-dev";
-my $cvs = "http://dev.apache.org/from-cvs/apache-$ver/";
+my $cvs = "http://cvs.apache.org/snapshots/apache-$ver/";
my $filptn = "apache-$ver\_";
rmtree $dir;
1.3 +513 -461 httpd-site/docs/dev/how-to-release.html
Index: how-to-release.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/dev/how-to-release.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- how-to-release.html 2001/11/22 00:55:16 1.2
+++ how-to-release.html 2001/11/24 07:15:54 1.3
@@ -1,498 +1,550 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
- <HEAD>
- <TITLE>How to build a release of Apache</TITLE>
- </HEAD>
-<!-- Yeah, we know; there are some HTML "lint-errors" in this -->
-<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
- <BODY
- BGCOLOR="#FFFFFF"
- TEXT="#000000"
- LINK="#0000FF"
- VLINK="#000080"
- ALINK="#FF0000"
- >
-<!--#include virtual="header.html" -->
-<P>
-<BR>
-
-<div align=center>
-<H1>How to build a release of Apache</H1>
-Alexei Kosut <akosut@apache.org><BR>
-Ralf S. Engelschall <rse@apache.org><BR>
-Jim Jagielski <jim@apache.org><br>
-Ken Coar <coar@apache.org>
-Martin Kraemer <martin@apache.org><br>
-</DIV>
-
-<BLOCKQUOTE>
-<BLOCKQUOTE>
-<BLOCKQUOTE>
-This document describes the typical release cycle the release manager has to
-step through when creating a new Apache release. It is written down as a
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+ <meta name="author" content="Documentation Group" /><meta name="email" content="docs@httpd.apache.org" />
+ <title>How to build a release of Apache - The Apache HTTP Server Project</title>
+ </head>
+ <body bgcolor="#ffffff" text="#000000" link="#525D76">
+<p><a href="/"><img src="../images/httpd_logo_wide.gif" alt="The Apache HTTP Server Project" border="0"/></a></p>
+ <table border="0" width="100%" cellspacing="4">
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td valign="top" nowrap="nowrap">
+ <p><b>Essentials</b></p>
+ <menu compact="compact">
+ <li><a href="/ABOUT_APACHE.html">About</a></li>
+ <li><a href="http://www.apache.org/LICENSE.txt">License</a></li>
+ <li><a href="/docs/misc/FAQ.html">FAQ</a></li>
+ <li><a href="/security_report.html">Security<br />Reports</a></li>
+ </menu>
+ <p><b><a
+href="/dev/">Developer Info</a></b></p>
+ <p><b><a
+href="http://www.apache.org/dist/httpd/">Download!</a></b></p>
+ <p><b><a
+href="/docs-project/">Documentation</a></b></p>
+ <menu compact="compact">
+ <li><a href="/docs/">Apache 1.3</a></li>
+ <li><a href="/docs-2.0/">Apache 2.0</a></li>
+ </menu>
+ <p><b>Subprojects</b></p>
+ <menu compact="compact">
+ <li><a href="/docs-project/">Docs</a></li>
+ <li><a href="/test/">Test</a></li>
+ </menu>
+ <p><b><a
+href="/info/">Miscellaneous</a></b></p>
+ <menu compact="compact">
+ <li><a href="/contributors/">Contributors</a></li>
+ <li><a href="/awards.html">Awards</a></li>
+ <li><a href="/in_the_news.html">In the News</a></li>
+ <li><a href="http://nav.webring.yahoo.com/hub?ring=apachesupport&id=12&hub">Support<br />Webring</a></li>
+ </menu>
+ </td>
+ <!-- RIGHT SIDE INFORMATION -->
+ <td align="left" valign="top">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <strong>How to build a release of Apache</strong>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p>
+Alexei Kosut <akosut@apache.org><br />
+Ralf S. Engelschall <rse@apache.org><br />
+Jim Jagielski <jim@apache.org><br />
+Ken Coar <coar@apache.org><br />
+Martin Kraemer <martin@apache.org><br />
+</p>
+<p>This document describes the typical release cycle the release manager has
+to step through when creating a new Apache release. It is written down as a
step-by-step instruction list and should be followed exactly as specified to
avoid problems or inconsistencies both in the created tarballs and the source
-repository.
-</BLOCKQUOTE>
-</BLOCKQUOTE>
-</BLOCKQUOTE>
-
-<P>
-<BR>
- <H2><A NAME="tarball">How to build an Apache Unix release</A></H2>
-
-<P><FONT COLOR="red">Note:</FONT> The below assumes that you are
-using <CODE>ssh</CODE> to login to your <CODE>httpd.apache.org</CODE>
+repository.</p>
+ </blockquote>
+ </td></tr>
+</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="unix"><strong>How to build an Apache Unix release</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p><font color="red">Note:</font> The below assumes that you are
+using <code>ssh</code> to login to your <code>httpd.apache.org</code>
account. If you are "rolling the tarball" remotely, the differences
-will be noted.
-
-<P><FONT COLOR="red">Important:</FONT> Once tagged and the tarball
-is rolled, there is <B>no going back</B>. If there are
+will be noted.</p>
+<p><font color="red">Important:</font> Once tagged and the tarball
+is rolled, there is <b>no going back</b>. If there are
problems with the tarball, the version number (either the rev-level
-or beta-level) <EM>must</EM> be bumped resulting in a new tag,
-tarball and release.
-
-<OL>
- <HR>
- <LI> Checkout the Apache source if needed into a scratch directory:<BR>
- <CODE><B>$ cvs checkout -P apache-1.<EM>X</EM></B></CODE>
- <br>
+or beta-level) <em>must</em> be bumped resulting in a new tag,
+tarball and release.</p>
+<hr />
+<ol>
+ <li>Checkout the Apache source if needed into a scratch directory:<br />
+ <code><b>$ cvs checkout -P apache-1.<em>X</em></b></code>
+ <br />
Note that the current <code><b>httpd-docs-1.3/htdocs</b></code>
documentation tree is automatically extracted into
- <CODE><B>apache-1.<EM>X</EM>/htdocs/</B></CODE>
+ <code><b>apache-1.<em>X</em>/htdocs/</b></code>
(two macros in the cvs configuration file
- <CODE><B>/home/cvs/CVSROOT/modules</B></CODE> do that for you).
- <P>
- For Apache 2.0:<BR>
- <CODE><B>$ cvs checkout -P httpd-2.<EM>X</EM></B></CODE>
- <br>
- <code><b>$ cd httpd-2.<i>X</i>/srclib</b></code>
- <br>
- <code><b>$ cvs checkout apr apr-util</b></code>
- <P>
- <LI> cd into the <CODE>apache</CODE> CVS tree.<BR>
- <CODE><B>$ cd apache-1.<EM>X</EM></B></CODE><BR>
- or<BR>
- <CODE><B>$ cd httpd-2.<EM>X</EM></B></CODE>
- <P><b>[ Adjusting Announcement to taste ]</b><br>
- <LI>
+ <code><b>/home/cvs/CVSROOT/modules</b></code> do that for you).
<p>
- <ul>
- <li>A prototype <code>Announcement</code> is included in
+ For Apache 2.<em>X</em>:<br />
+ <code><b>$ cvs checkout -P httpd-2.<em>X</em></b></code><br />
+ <code><b>$ cd httpd-2.<i>X</i>/srclib</b></code><br />
+ <code><b>$ cvs checkout apr apr-util</b></code>
+ </p>
+ </li>
+ <li>cd into the <code>apache</code> CVS tree.<br />
+ <code><b>$ cd apache-1.<em>X</em></b></code><br />
+ or<br />
+ <code><b>$ cd httpd-2.<em>X</em></b></code>
+ </li>
+ <li>Adjust Announcement to taste.<br />
+ <p>A prototype <code>Announcement</code> is included in
the main CVS source tree. This file should be updated
to reflect the current state of affairs concerning the
release. For example, the Release Version should reflect
what is actually being announced. Also, the key enhancements
- of the Release should be noted.<br>
- <code><b>$ vi Announcement</b></code><br>
- <code><b>$ cvs commit Announcement</b></code><br>
- <p>
- <b>Note:</b> This document is also present in the
+ of the Release should be noted.<br />
+ <code><b>$ vi Announcement</b></code><br />
+ <code><b>$ cvs commit Announcement</b></code><br />
+ <p><b>Note:</b> This document is also present in the
<code>httpd-dist</code> cvs module, both in HTML and plain
- text form. You may want to create one version out of the other.
- </ul>
- <HR>
- <B>[ Only for final releases, not for internal pre-releases ]</B><BR>
- <P>
- <LI> For Apache 1.3<BR>
- Change <CODE>SERVER_BASEREVISION</CODE> in <TT>src/include/httpd.h</TT>
- from ``<CODE>Apache/1.<EM>X.Y</EM>-dev</CODE>'' to
- ``<CODE>Apache/1.<EM>X.Y</EM></CODE>''. Then also change
- <CODE>APACHE_RELEASE</CODE> in the same file from
- ``<CODE>1<EM>XXYY0</EM>00</CODE>'' to ``<CODE>1<EM>XXYY1</EM>00</CODE>''.
+ text form. You may want to create one version out of the other.</p>
+ </p>
+ </li>
+ <li>Change the version number to indicate a release.<br />
+ <p>For Apache 1.3<br />
+ Change <code>SERVER_BASEREVISION</code> in <TT>src/include/httpd.h</TT>
+ from ``<code>Apache/1.<em>X.Y</em>-dev</code>'' to
+ ``<code>Apache/1.<em>X.Y</em></code>''. Then also change
+ <code>APACHE_RELEASE</code> in the same file from
+ ``<code>1<em>XXYY0</em>00</code>'' to ``<code>1<em>XXYY1</em>00</code>''.
The format is something like
- <CODE>printf("%d%02d%02d%d%02d", major, minor, bugfix, final,
- beta)</CODE>. <BR>
- <CODE><B>$ vi src/include/httpd.h</B></CODE><BR>
- <CODE><B>$ cvs commit src/include/httpd.h</B></CODE>
- <P>
- For Apache 2.0:<BR>
- Change <CODE>SERVER_BASEREVISION</CODE> in <TT>include/httpd.h</TT>
- from ``<CODE>2.<EM>X</EM>-dev</CODE>'' to ``<CODE>2.<EM>X</EM></CODE>''.
- Then also change <CODE>APACHE_RELEASE</CODE> in the same file from
- ``<CODE>2<EM>XXYY0</EM>00</CODE>'' to ``<CODE>2<EM>XXYY1</EM>00</CODE>''.
- <P>
- <STRONG>Note:</STRONG> until Apache 2.0 is of general release quality,
- module magic numbers are not enforced. You must edit <TT>include/ap_mmn.h</TT>
- and bump the MODULE_MAGIC_NUMBER_MAJOR prior to rolling the tarball, to assure
- beta testers are testing the corresponding .so modules. <I>This policy will be
- retracted, and coders will be reponsible for mmn bumps, once Apache 2.0 is
- officially released.</I>
- <P>
- <LI> Make sure your PGP keys are already present in the <CODE>KEYS</CODE>
+ <code>printf("%d%02d%02d%d%02d", major, minor, bugfix, final,
+ beta)</code>. <br />
+ <code><b>$ vi src/include/httpd.h</b></code><br />
+ <code><b>$ cvs commit src/include/httpd.h</b></code>
+ </p>
+ <p>For Apache 2.0:<br />
+ Change <code>SERVER_BASEREVISION</code> in <TT>include/httpd.h</TT>
+ from ``<code>2.<em>X</em>-dev</code>'' to ``<code>2.<em>X</em></code>''.
+ Then also change <code>APACHE_RELEASE</code> in the same file from
+ ``<code>2<em>XXYY0</em>00</code>'' to ``<code>2<em>XXYY1</em>00</code>''.
+ </p>
+ <p><STRONG>Note:</STRONG> until Apache 2.0 is of general release quality,
+ module magic numbers are not enforced. You must edit
+ <TT>include/ap_mmn.h</TT> and bump the MODULE_MAGIC_NUMBER_MAJOR prior
+ to rolling the tarball, to assure beta testers are testing the
+ corresponding .so modules. <I>This policy will be retracted, and
+ coders will be reponsible for mmn bumps, once Apache 2.0 is officially
+ released.</I>
+ </p>
+ </li>
+ <li>Make sure your PGP keys are already present in the <code>KEYS</code>
file. If they are not, extract your public key using the
- ``<CODE>pgp -kxa</CODE>'' command, add them to the
- <CODE>KEYS</CODE> file and commit it before tagging.
- <P>
- <LI> Tag the sources for this release:<BR>
- (<EM>note: be sure to tag the whole thing, not just <CODE>src</CODE></EM>!)<BR>
- <CODE><B>$ cvs tag APACHE_1_<EM>X_Y</EM></B></CODE><BR>
- For Apache 2.0:<BR>
- <CODE><B>$ cvs tag APACHE_2_<EM>X_Y</EM></B></CODE>
- <P>
- <HR>
- <B>[ For all releases ]</B><BR>
- <P>
- <LI> Make an export version of the distribution: (this creates a second
- subdirectory <CODE>apache-Z.<EM>X.Y</EM></CODE> for the exported version
- beside the existing CVS tree in <CODE>apache-Z.<EM>X</EM></CODE>)<BR>
- For Apache 1.3:<BR>
- <CODE><B>$ cd ..</B></CODE><BR>
- <CODE><B>$ umask 022</B></CODE><BR>
- <CODE><B>$ cvs export -r APACHE_1_<EM>X_Y</EM> -d apache_1.<EM>X.Y</EM> apache-1.<EM>X</EM></B></CODE><BR>
- <CODE><B>$ cd apache_1.<EM>X.Y</EM></B></CODE><BR>
+ ``<code>pgp -kxa</code>'' command, add them to the
+ <code>KEYS</code> file and commit it before tagging.
+ </li>
+ <li>Tag the sources for this release:<br />
+ (<em>note: be sure to tag the whole thing, not just
+ <code>src</code></em>!)<br />
+ <code><b>$ cvs tag APACHE_1_<em>X_Y</em></b></code><br />
+ For Apache 2.0:<br />
+ <code><b>$ cvs tag APACHE_2_<em>X_Y</em></b></code>
+ </li>
+ <li>Make an export version of the distribution: (this creates a second
+ subdirectory <code>apache-Z.<em>X.Y</em></code> for the exported version
+ beside the existing CVS tree in <code>apache-Z.<em>X</em></code>)<br />
+ <p>For Apache 1.3:<br />
+ <code><b>$ cd ..</b></code><br />
+ <code><b>$ umask 022</b></code><br />
+ <code><b>$ cvs export -r APACHE_1_<em>X_Y</em> -d apache_1.<em>X.Y</em> apache-1.<em>X</em></b></code><br />
+ <code><b>$ cd apache_1.<em>X.Y</em></b></code><br />
Again, the current <code><b>httpd-docs-1.3/htdocs</b></code>
documentation tree is automatically extracted into
- <CODE><B>apache-1.<EM>X.Y</EM>/htdocs/</B></CODE> for you.
- <UL>
-
- <LI><FONT COLOR="red">Note:</FONT> There is a known problem
- using <CODE>cvs export</CODE> remotely with <CODE>cvs-1.9</CODE>
- and later. If this affects you, you will need to do a checkout
- instead:<BR>
- <CODE><B>$ umask 022</B></CODE><BR>
- <CODE><B>$ cvs checkout -r APACHE_1_<EM>X_Y</EM> -d apache_1.<EM>X.Y</EM> apache-1.<EM>X</EM></B></CODE><BR>
- <CODE><B>$ cd apache_1.<EM>X.Y</EM></B></CODE><BR>
- <code><b>$ cvs checkout -r APACHE_1<i>X_Y</i> -d htdocs httpd-docs-1.3/htdocs</b></code>
-
- </UL>
-
- <P>
- For Apache 2.0:<BR>
- <CODE><B>$ cd ..</B></CODE><BR>
- <CODE><B>$ umask 022</B></CODE><BR>
- <CODE><B>$ cvs export -r APACHE_2_<EM>X_Y</EM> -d apache_2.<EM>X.Y</EM> httpd-2.<EM>X</EM></B></CODE><BR>
- <CODE><B>$ cd apache_2.<EM>X.Y</EM>/srclib</B></CODE><BR>
- <code><b>$ cvs export -r APACHE_2_<i>X_Y</i> apr apr-util</code>
-
- <UL>
-
- <LI><FONT COLOR="red">Note:</FONT> There is a known problem
- using <CODE>cvs export</CODE> remotely with <CODE>cvs-1.9</CODE>
- and later. If this affects you, you will need to do a checkout
- instead:<BR>
- <CODE><B>$ umask 022</B></CODE><BR>
- <CODE><B>$ cvs checkout -r APACHE_2_<EM>X_Y</EM> -d apache_2.<EM>X.Y</EM> httpd-2.<EM>X</EM></B></CODE><BR>
- <CODE><B>$ cd apache_2.<EM>X.Y</EM>/srclib</B></CODE><BR>
- <code><b>$ cvs checkout -r APACHE_2<i>X_Y</i> apr apr-util</b></code>
-
- </UL>
- <P>
- <LI> Make sure the master site's FAQ is up-to-date:<br>
+ <code><b>apache-1.<em>X.Y</em>/htdocs/</b></code> for you.
+ <ul>
+ <!-- Who has cvs-1.9 now? - jre -->
+ <li><font color="red">Note:</font> There is a known problem
+ using <code>cvs export</code> remotely with <code>cvs-1.9</code>
+ and later. If this affects you, you will need to do a checkout
+ instead:<br />
+ <code><b>$ umask 022</b></code><br />
+ <code><b>$ cvs checkout -r APACHE_1_<em>X_Y</em> -d apache_1.<em>X.Y</em> apache-1.<em>X</em></b></code><br />
+ <code><b>$ cd apache_1.<em>X.Y</em></b></code><br />
+ <code><b>$ cvs checkout -r APACHE_1<i>X_Y</i> -d htdocs httpd-docs-1.3/htdocs</b></code>
+ </li>
+ </ul>
+ </p>
+
+ <p>For Apache 2.0:<br />
+ <code><b>$ cd ..</b></code><br />
+ <code><b>$ umask 022</b></code><br />
+ <code><b>$ cvs export -r APACHE_2_<em>X_Y</em> -d apache_2.<em>X.Y</em> httpd-2.<em>X</em></b></code><br />
+ <code><b>$ cd apache_2.<em>X.Y</em>/srclib</b></code><br />
+ <code><b>$ cvs export -r APACHE_2_<i>X_Y</i> apr apr-util</b></code>
+ <ul>
+ <li><font color="red">Note:</font> There is a known problem
+ using <code>cvs export</code> remotely with <code>cvs-1.9</code>
+ and later. If this affects you, you will need to do a checkout
+ instead:<br />
+ <code><b>$ umask 022</b></code><br />
+ <code><b>$ cvs checkout -r APACHE_2_<em>X_Y</em> -d apache_2.<em>X.Y</em> httpd-2.<em>X</em></b></code><br />
+ <code><b>$ cd apache_2.<em>X.Y</em>/srclib</b></code><br />
+ <code><b>$ cvs checkout -r APACHE_2<i>X_Y</i> apr apr-util</b></code>
+ </li>
+ </ul>
+ </p>
+ </li>
+ <li>Make sure the master site's FAQ is up-to-date:<br />
<code><b>$ (cd /www/httpd.apache.org/docs/misc ; cvs update)</b></code>
- <p>
- <li> Extract the FAQ as a single file, as it appears on the Web:<br>
+ </li>
+ <li>Extract the FAQ as a single file, as it appears on the Web:<br />
<code><b>$ links -source http://httpd.apache.org/docs/misc/FAQ.html
> htdocs/manual/misc/FAQ.html</b></code>
- <p>
-
- <LI> For Apache 1.3:<BR>
- Create <CODE>src/Configuration</CODE> file: (1.3.x only)<BR>
- <CODE><B>$ cp src/Configuration.tmpl src/Configuration</B></CODE>
- <P>
- For Apache 2.0:<BR>
- Create <CODE>./configure</CODE> file, and remove all symlinks<BR>
- <CODE><B>$ ./buildconf</B></CODE><BR>
- <CODE><B>$ rm -f ltconfig ltmain.sh config.sub config.guess</B></CODE><BR>
- <CODE><B>$ cp /usr/local/share/libtool/ltconfig .</B></CODE><BR>
- <CODE><B>$ cp /usr/local/share/libtool/ltmain.sh .</B></CODE><BR>
- <CODE><B>$ cp /usr/local/share/libtool/config.sub .</B></CODE><BR>
- <CODE><B>$ cp /usr/local/share/libtool/config.guess .</B></CODE><BR>
- <P>
- <LI> Remove <CODE>STATUS</CODE>, <CODE>RULES.CVS</CODE>,
- <CODE>src/INDENT</CODE>, the multi-part FAQ, various
- <CODE>.cvsignore</CODE> and
+ </li>
+ <li>Create the configuration files:<br />
+ <p>For Apache 1.3:<br />
+ Create <code>src/Configuration</code> file:<br />
+ <code><b>$ cp src/Configuration.tmpl src/Configuration</b></code>
+ </p>
+ <p>For Apache 2.0:<br />
+ Create <code>./configure</code> file, and remove all symlinks<br />
+ <code><b>$ ./buildconf</b></code><br />
+ <!-- Hmm. Why do we have to do the rm -f if buildconf should do that
+ for us? - jre -->
+ <code><b>$ rm -f ltconfig ltmain.sh config.sub config.guess</b></code><br />
+ <code><b>$ cp /usr/local/share/libtool/ltconfig .</b></code><br />
+ <code><b>$ cp /usr/local/share/libtool/ltmain.sh .</b></code><br />
+ <code><b>$ cp /usr/local/share/libtool/config.sub .</b></code><br />
+ <code><b>$ cp /usr/local/share/libtool/config.guess .</b></code><br />
+ </p>
+ </li>
+ <li>Remove <code>STATUS</code>, <code>RULES.CVS</code>,
+ <code>src/INDENT</code>, the multi-part FAQ, various
+ <code>.cvsignore</code> and
the developer's test subdirectories. Depending on which version you
- are releasing, not all of these files will be in the repository:<BR>
- <CODE><B>$ rm STATUS RULES.CVS src/INDENT
- htdocs/manual/misc/FAQ-*.html</B></CODE><BR>
- <CODE><B>$ find . -name ".cvsignore" -exec rm {} \;</B></CODE><BR>
- <CODE><B>$ find . -type d -name "test" -exec rm -Rf {} \;</B></CODE>
-
- <UL>
-
- <LI><FONT COLOR="red">Note:</FONT> If you needed to do a
- <CODE>checkout</CODE> instead of a <CODE>export</CODE>, you
- will also need to remove the CVS administrative files:<BR>
- <CODE><B>$ find . -type d -name "CVS" -exec rm -rf {} \;</B></CODE>
-
- </UL>
- <P>
- <LI> Expand the Server-Side-Include directives in the manual:<BR>
- <CODE><B>$ cd htdocs/manual</B></CODE><BR>
- <CODE><B>$ ./expand.pl</B></CODE><BR>
- <CODE><B>$ rm ./expand.pl</B></CODE><BR>
- <CODE><B>$ cd ../../..</B></CODE>
- <P>
- <LI> Roll the distribution tarball:<BR>
- <CODE><B>$ tar cvf apache_<EM>Z.X.Y</EM>.tar apache_<EM>Z.X.Y</EM></B></CODE><BR>
- <P>
- <LI> Make the final packed distribution files:<BR>
- <CODE><B>$ cp -p apache_<EM>Z.X.Y</EM>.tar xapache_<EM>Z.X.Y</EM>.tar</B></CODE><BR>
- <CODE><B>$ gzip -9 apache_<EM>Z.X.Y</EM>.tar</B></CODE><BR>
- <CODE><B>$ mv xapache_<EM>Z.X.Y</EM>.tar apache_<EM>Z.X.Y</EM>.tar</B></CODE><BR>
- <CODE><B>$ compress apache_<EM>Z.X.Y</EM>.tar</B></CODE><BR>
- <P>
- <LI> Test the packed tar files and check for errors:<BR>
- <CODE><B>$ gunzip -c apache_<EM>Z.X.Y</EM>.tar.gz | tar tvf -</B></CODE><BR>
- (or simply: <CODE><B>$ tar tvzf apache_<EM>Z.X.Y</EM>.tar.gz</B></CODE>)<BR>
- <CODE><B>$ uncompress <apache_<EM>Z.X.Y</EM>.tar.Z | tar tvf -</B></CODE><BR>
- <P>
- <LI> Sign the distribution files:<BR>
- <CODE><B>$ pgp -sba apache_<EM>Z.X.Y</EM>.tar.gz</B></CODE><BR>
- <CODE><B>$ pgp -sba apache_<EM>Z.X.Y</EM>.tar.Z</B></CODE><BR>
-
- <UL>
-
- <LI><FONT COLOR="red">Note:</FONT> Be sure your PGP key is already in the
- <CODE>KEYS</CODE> file!<BR>
-
- </UL>
- <P>
- <LI> Test the tarball signatures:<BR>
- <CODE><B>$ pgp apache_<EM>Z.X.Y</EM>.tar.gz.asc apache_<EM>Z.X.Y</EM>.tar.gz</B></CODE><BR>
- <CODE><B>$ pgp apache_<EM>Z.X.Y</EM>.tar.Z.asc apache_<EM>Z.X.Y</EM>.tar.Z</B></CODE><BR>
- <P>
- <LI> Remember the CHANGES file:<BR>
- <CODE><B>$ cp apache_<EM>Z.X.Y</EM>/src/CHANGES ./CHANGES_<EM>Z.X</EM></B></CODE>
- <P>
- <LI> Cleanup:<BR>
- (this deletes the export tree: it is now no longer
- required. We still need the CVS tree, see below)<BR>
- <CODE><B>$ rm -fr apache_<EM>Z.X.Y</EM></B></CODE>
- <P>
- <LI> Make the tarball available for testing purposes
- (in <A HREF="http://httpd.apache.org/dev/dist/">http://httpd.apache.org/dev/dist/</A>):<BR>
- <CODE><B>$ chmod 664 CHANGES_<EM>Z.X</EM> apache_<EM>Z.X.Y</EM>.tar.*</B></CODE><BR>
- <CODE><B>$ cp -pv apache_<EM>Z.X.Y</EM>.tar.gz /www/httpd.apache.org/dev/dist/</B></CODE><BR>
- <CODE><B>$ cp -pv apache_<EM>Z.X.Y</EM>.tar.gz.asc /www/httpd.apache.org/dev/dist/</B></CODE><BR>
- <CODE><B>$ cp -pv apache_<EM>Z.X.Y</EM>.tar.Z /www/httpd.apache.org/dev/dist/</B></CODE><BR>
- <CODE><B>$ cp -pv apache_<EM>Z.X.Y</EM>.tar.Z.asc /www/httpd.apache.org/dev/dist/</B></CODE><BR>
- <CODE><B>$ chmod g+w /www/httpd.apache.org/dev/dist/apache_<EM>Z.X.Y</EM>.tar.*</B></CODE><BR>
-
- <UL>
+ are releasing, not all of these files will be in the repository:<br />
+ <code><b>$ rm STATUS RULES.CVS src/INDENT
+ htdocs/manual/misc/FAQ-*.html</b></code><br />
+ <code><b>$ find . -name ".cvsignore" -exec rm {} \;</b></code><br />
+ <code><b>$ find . -type d -name "test" -exec rm -Rf {} \;</b></code>
+ <ul>
+ <li><font color="red">Note:</font> If you needed to do a
+ <code>checkout</code> instead of a <code>export</code>, you
+ will also need to remove the CVS administrative files:<br />
+ <code><b>$ find . -type d -name "CVS" -exec rm -rf {} \;</b></code>
+ </li>
+ </ul>
+ </li>
+ <li>Expand the Server-Side-Include directives in the manual:<br />
+ <code><b>$ cd htdocs/manual</b></code><br />
+ <code><b>$ ./expand.pl</b></code><br />
+ <code><b>$ rm ./expand.pl</b></code><br />
+ <code><b>$ cd ../../..</b></code>
+ </li>
+ <li>Roll the distribution tarball:<br />
+ <code><b>$ tar cvf apache_<em>Z.X.Y</em>.tar apache_<em>Z.X.Y</em></b></code><br />
+ </li>
+ <li>Make the final packed distribution files:<br />
+ <code><b>$ cp -p apache_<em>Z.X.Y</em>.tar xapache_<em>Z.X.Y</em>.tar</b></code><br />
+ <code><b>$ gzip -9 apache_<em>Z.X.Y</em>.tar</b></code><br />
+ <code><b>$ mv xapache_<em>Z.X.Y</em>.tar apache_<em>Z.X.Y</em>.tar</b></code><br />
+ <code><b>$ compress apache_<em>Z.X.Y</em>.tar</b></code><br />
+ </li>
+ <li>Test the packed tar files and check for errors:<br />
+ <code><b>$ gunzip -c apache_<em>Z.X.Y</em>.tar.gz | tar tvf -</b></code><br />
+ (or simply: <code><b>$ tar tvzf apache_<em>Z.X.Y</em>.tar.gz</b></code>)<br />
+ <code><b>$ uncompress <apache_<em>Z.X.Y</em>.tar.Z | tar tvf -</b></code><br />
+ </li>
+ <li>Sign the distribution files:<br />
+ <code><b>$ pgp -sba apache_<em>Z.X.Y</em>.tar.gz</b></code><br />
+ <code><b>$ pgp -sba apache_<em>Z.X.Y</em>.tar.Z</b></code><br />
- <LI><FONT COLOR="red">Note:</FONT> If rolling the tarball
- remotely, you should use <CODE>scp</CODE> to place them
- in <CODE>httpd.apache.org</CODE> in the
- <CODE>/www/httpd.apache.org/dev/dist/</CODE>
- directory.
+ <ul>
+ <li><font color="red">Note:</font> Be sure your PGP key is already in
+ the <code>KEYS</code> file!
+ </li>
+ </ul>
+ </li>
+ <li>Test the tarball signatures:<br />
+ <code><b>$ pgp apache_<em>Z.X.Y</em>.tar.gz.asc apache_<em>Z.X.Y</em>.tar.gz</b></code><br />
+ <code><b>$ pgp apache_<em>Z.X.Y</em>.tar.Z.asc apache_<em>Z.X.Y</em>.tar.Z</b></code><br />
+ </li>
+ <li>Remember the CHANGES file:<br />
+ <code><b>$ cp apache_<em>Z.X.Y</em>/src/CHANGES ./CHANGES_<em>Z.X</em></b></code>
+ </li>
+ <li>Cleanup:<br />
+ (this deletes the export tree: it is now no longer required. We
+ still need the CVS tree, see below)<br />
+ <code><b>$ rm -fr apache_<em>Z.X.Y</em></b></code>
+ </li>
+ <li>Make the tarball available for testing purposes
+ (in <a href="http://httpd.apache.org/dev/dist/">http://httpd.apache.org/dev/dist/</a>):<br />
+ <code><b>$ chmod 664 CHANGES_<em>Z.X</em> apache_<em>Z.X.Y</em>.tar.*</b></code><br />
+ <code><b>$ cp -pv apache_<em>Z.X.Y</em>.tar.gz /www/httpd.apache.org/dev/dist/</b></code><br />
+ <code><b>$ cp -pv apache_<em>Z.X.Y</em>.tar.gz.asc /www/httpd.apache.org/dev/dist/</b></code><br />
+ <code><b>$ cp -pv apache_<em>Z.X.Y</em>.tar.Z /www/httpd.apache.org/dev/dist/</b></code><br />
+ <code><b>$ cp -pv apache_<em>Z.X.Y</em>.tar.Z.asc /www/httpd.apache.org/dev/dist/</b></code><br />
+ <code><b>$ chmod g+w /www/httpd.apache.org/dev/dist/apache_<em>Z.X.Y</em>.tar.*</b></code><br />
- </UL>
- <P>
- <HR>
- <B>[ Only for final releases, not for internal pre-releases ]</B><BR>
- <P>
- <LI> cd back into the CVS tree location.<BR>
- <CODE><B>$ cd apache-<EM>Z.X</EM></B></CODE>
- <P>
- <LI> For Apache 1.3:<BR>
- Change <CODE>SERVER_BASEREVISION</CODE> in <CODE>src/include/httpd.h</CODE>
- from ``<CODE>Apache/1.<EM>X.Y</EM></CODE>'' to
- ``<CODE>Apache/1.<EM>X.(Y+1)</EM>-dev</CODE>'' and change
- <CODE>APACHE_RELEASE</CODE> to <CODE>1<EM>XX(YY+1)</EM>000</CODE>.<BR>
+ <ul>
+ <li><font color="red">Note:</font> If rolling the tarball
+ remotely, you should use <code>scp</code> to place them
+ in <code>httpd.apache.org</code> in the
+ <code>/www/httpd.apache.org/dev/dist/</code>
+ directory.
+ </li>
+ </ul>
+ </li>
+ <li>Bump the version number to the next version and indicate we are
+ in development.<br />
+ cd back into the CVS tree location.<br />
+ <code><b>$ cd apache-<em>Z.X</em></b></code>
+ <p>For Apache 1.3:<br />
+ Change <code>SERVER_BASEREVISION</code> in <code>src/include/httpd.h</code>
+ from ``<code>Apache/1.<em>X.Y</em></code>'' to
+ ``<code>Apache/1.<em>X.(Y+1)</em>-dev</code>'' and change
+ <code>APACHE_RELEASE</code> to <code>1<em>XX(YY+1)</em>000</code>.<br />
(1.3.x only) Additionally make sure that the Configure script's version
- knowledge for the <CODE>SHARED_CORE</CODE> reflects the new
+ knowledge for the <code>SHARED_CORE</code> reflects the new
version.revision.patchlevel triple.
- Look for the line ``<CODE>V=1 R=<EM>X</EM> P=<EM>Y</EM></CODE>''
- inside <CODE>src/Configure</CODE> and adjust it accordingly.<BR>
+ Look for the line ``<code>V=1 R=<em>X</em> P=<em>Y</em></code>''
+ inside <code>src/Configure</code> and adjust it accordingly.<br />
Finally, add a new line
- ``<CODE>Changes with Apache 1.<EM>X.(Y+1)</EM>:</CODE>'' to the
+ ``<code>Changes with Apache 1.<em>X.(Y+1)</em>:</code>'' to the
head of the <SAMP>src/CHANGES</SAMP> file for the
- forthcoming fixes in the new version.<BR>
- <CODE><B>$ vi src/include/httpd.h \<BR>
- src/Configure \<BR>
- src/CHANGES</B></CODE><BR>
- <CODE><B>$ cvs commit src/include/httpd.h \<BR>
- src/Configure \<BR>
- src/CHANGES</B></CODE><BR>
- <BR>
+ forthcoming fixes in the new version.<br />
+ <code><b>$ vi src/include/httpd.h \<br />
+ src/Configure \<br />
+ src/CHANGES</b></code><br />
+ <code><b>$ cvs commit src/include/httpd.h \<br />
+ src/Configure \<br />
+ src/CHANGES</b></code><br />
+ <br />
Edit the <SAMP>STATUS</SAMP> file and update the status for the
- tagged apache_1.<EM>X.Y</EM> version, and add a header line
- for the new apache_1.<EM>X.(Y+1)</EM> version<BR>
- <CODE><B>$ vi STATUS</B></CODE><BR>
- <CODE><B>$ cvs commit STATUS</B></CODE><BR>
- <BR>
- <CODE><B>$ cd ..</B></CODE><BR>
- <P>
- For Apache 2.0:<BR>
- Change <CODE>SERVER_BASEREVERSION</CODE> in <CODE>include/httpd.h</CODE>
- from ``<CODE>2.<EM>X.Y</EM></CODE>'' to
- ``<CODE>2.<EM>X.(Y+1)</EM>-dev</CODE>'' and change
- <CODE>APACHE_RELEASE</CODE> to <CODE>1<EM>XX(YY+1)</EM>000</CODE>.<BR>
+ tagged apache_1.<em>X.Y</em> version, and add a header line
+ for the new apache_1.<em>X.(Y+1)</em> version<br />
+ <code><b>$ vi STATUS</b></code><br />
+ <code><b>$ cvs commit STATUS</b></code><br />
+ <br />
+ <code><b>$ cd ..</b></code><br />
+ </p>
+ <p>
+ For Apache 2.0:<br />
+ Change <code>SERVER_BASEREVERSION</code> in <code>include/httpd.h</code>
+ from ``<code>2.<em>X.Y</em></code>'' to
+ ``<code>2.<em>X.(Y+1)</em>-dev</code>'' and change
+ <code>APACHE_RELEASE</code> to <code>1<em>XX(YY+1)</em>000</code>.<br />
Finally, add a new line
- ``<CODE>Changes with Apache 1.<EM>X.(Y+1)</EM>:</CODE>'' to the
+ ``<code>Changes with Apache 1.<em>X.(Y+1)</em>:</code>'' to the
head of the <SAMP>CHANGES</SAMP> file for the
- forthcoming fixes in the new version.<BR>
- <CODE><B>$ vi include/httpd.h \<BR>
- src/CHANGES</B></CODE><BR>
- <CODE><B>$ cvs commit include/httpd.h \<BR>
- CHANGES</B></CODE><BR>
- <CODE><B>$ cd ..</B></CODE><BR>
- <P>
- <HR>
- <LI> Cleanup:<BR>
+ forthcoming fixes in the new version.<br />
+ <code><b>$ vi include/httpd.h \<br />
+ CHANGES</b></code><br />
+ <code><b>$ cvs commit include/httpd.h \<br />
+ CHANGES</b></code><br />
+ <code><b>$ cd ..</b></code><br />
+ </p>
+ </li>
+ <li>Cleanup:<br />
(delete the CVS tree, after verification that it does not
- contain any uncommitted changes)<BR>
- <CODE><B>$ cvs release -d apache-<EM>Z.X</EM></B></CODE>
- <P>
-<B>[ Now wait for the group to test and approve the tarball ]</B>
- <HR>
- <B>[ Final release steps <U>after</U> the group has approved the tarball ]</B><BR>
- <P>
-
-<EM><FONT COLOR="red">Note:</FONT> Do not continue with the rest of
-these instructions until the group really approves the tarball !</EM>
-
- <P>
- <LI> Make the distribution available
- (in <A HREF="http://www.apache.org/dist/httpd/">http://www.apache.org/dist/httpd/</A>)
- Z is either 1 or 2:<BR>
- <CODE><B>$ cp CHANGES_<EM>Z.X</EM> /www/www.apache.org/dist/httpd/CHANGES_<EM>Z.X</EM></B></CODE><BR>
- <CODE><B>$ cp apache_<EM>Z.X.Y</EM>.tar.gz /www/www.apache.org/dist/httpd/</B></CODE><BR>
- <CODE><B>$ cp apache_<EM>Z.X.Y</EM>.tar.gz.asc /www/www.apache.org/dist/httpd/</B></CODE><BR>
- <CODE><B>$ cp apache_<EM>Z.X.Y</EM>.tar.Z /www/www.apache.org/dist/httpd/</B></CODE><BR>
- <CODE><B>$ cp apache_<EM>Z.X.Y</EM>.tar.Z.asc /www/www.apache.org/dist/httpd/</B></CODE><BR>
-
- <UL>
-
- <LI><FONT COLOR="red">Note:</FONT> If rolling the tarball
- remotely, you should use <CODE>scp</CODE> to place them
- in <CODE>www.apache.org</CODE> in the
- <CODE>/www/www.apache.org/dist/httpd/</CODE> directory.
-
- </UL>
- If the Win32 binary is already built and tested at this point,
+ contain any uncommitted changes)<br />
+ <code><b>$ cvs release -d apache-<em>Z.X</em></b></code>
+ </li>
+</ol>
+<p><b>Now wait for the group to test and approve the tarball.</b></p>
+ </blockquote>
+ </td></tr>
+</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="release"><strong>Final release steps</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p><em><font color="red">Note:</font> Do not continue with the rest of
+these instructions until the group really approves the tarball!</em></p>
+<ol>
+ <li>Make the distribution available
+ (in <a href="http://www.apache.org/dist/httpd/">http://www.apache.org/dist/httpd/</a>)
+ Z is either 1 or 2:<br />
+ <code><b>$ cp CHANGES_<em>Z.X</em> /www/www.apache.org/dist/httpd/CHANGES_<em>Z.X</em></b></code><br />
+ <code><b>$ cp apache_<em>Z.X.Y</em>.tar.gz /www/www.apache.org/dist/httpd/</b></code><br />
+ <code><b>$ cp apache_<em>Z.X.Y</em>.tar.gz.asc /www/www.apache.org/dist/httpd/</b></code><br />
+ <code><b>$ cp apache_<em>Z.X.Y</em>.tar.Z /www/www.apache.org/dist/httpd/</b></code><br />
+ <code><b>$ cp apache_<em>Z.X.Y</em>.tar.Z.asc /www/www.apache.org/dist/httpd/</b></code><br />
+ <ul>
+ <li><font color="red">Note:</font> If rolling the tarball
+ remotely, you should use <code>scp</code> to place them
+ in <code>www.apache.org</code> in the
+ <code>/www/www.apache.org/dist/httpd/</code> directory.
+ </li>
+ </ul>
+ <p>If the Win32 binary is already built and tested at this point,
you can add it to the dist directory as well as to the
- <CODE>binaries/win32/</CODE> directory.
- <P>
- <LI> Checkout the
- <A HREF="http://www.apache.org/dist/httpd/">httpd-dist site</A>,
- if needed, into a scratch directory:<BR>
- <CODE><B>$ cvs -d cvs.apache.org:/home/cvs checkout -P httpd-dist</B></CODE>
- <P>
- <LI> Change directory into <CODE>httpd-dist</CODE><BR>
- <CODE><B>$ cd httpd-dist/</B></CODE>
- <P>
- <LI> Edit the files
- <A HREF="http://www.apache.org/dist/httpd/README.html"><CODE>README.html</CODE></A> and <A HREF="http://www.apache.org/dist/httpd/HEADER.html"><CODE>HEADER.html</CODE></A> as well as
- <A HREF="http://www.apache.org/dist/httpd/Announcement.html"><CODE>Announcement.html</CODE></A> and its plaintext equivalent
- <A HREF="http://www.apache.org/dist/httpd/Announcement.txt"><CODE>Announcement.txt</CODE></A> plus the
- <A HREF="http://www.apache.org/dist/httpd/.htaccess"><CODE>.htaccess</CODE></A> file (which defines the
- <CODE>AddDescription</CODE> comments)
- from the <CODE>apache-site</CODE> CVS tree
+ <code>binaries/win32/</code> directory.
+ </p>
+ </li>
+ <li>Checkout the
+ <a href="http://www.apache.org/dist/httpd/">httpd-dist site</a>,
+ if needed, into a scratch directory:<br />
+ <code><b>$ cvs -d cvs.apache.org:/home/cvs checkout -P httpd-dist</b></code>
+ </li>
+ <li>Change directory into <code>httpd-dist</code><br />
+ <code><b>$ cd httpd-dist/</b></code>
+ </li>
+ <li>Edit the files
+ <a href="http://www.apache.org/dist/httpd/README.html"><code>README.html</code></a> and <a href="http://www.apache.org/dist/httpd/HEADER.html"><code>HEADER.html</code></a> as well as
+ <a href="http://www.apache.org/dist/httpd/Announcement.html"><code>Announcement.html</code></a> and its plaintext equivalent
+ <a href="http://www.apache.org/dist/httpd/Announcement.txt"><code>Announcement.txt</code></a> plus the
+ <a href="http://www.apache.org/dist/httpd/.htaccess"><code>.htaccess</code></a> file (which defines the
+ <code>AddDescription</code> comments)
+ from the <code>apache-site</code> CVS tree
as required (all in the
- <A HREF="http://www.apache.org/dist/httpd/"><CODE>./dist</CODE></A>
- subdirectory). The <CODE>Announcement.*</CODE> files should be based on the <CODE>Announcement</CODE> file in the tagged CVS tree. For Apache 2.0,
- <CODE>Announcement</CODE> should be replaced with <CODE>Announcement2</CODE>:<BR>
-
- <CODE><B>$ vi README.html \<BR>
- HEADER.html \<BR>
- Announcement.html \<BR>
- Announcement.txt \<BR>
- .htaccess</B></CODE><BR>
- <P>
- <LI> Commit the changes:<BR>
- <CODE><B>$ cvs commit README.html \<br>
- HEADER.html \<br>
- Announcement.html \<BR>
- Announcement.txt \<BR>
- .htaccess</B></CODE><BR>
- <CODE><B>$ cd ../..</B></CODE>
- <P>
- <LI> Checkout the <A HREF="http://httpd.apache.org/">httpd site</A> if needed into a scratch directory:<BR>
- <CODE><B>$ cvs -d cvs.apache.org:/home/cvs checkout httpd-site</B></CODE>
- <P>
- <LI> cd into the <CODE>httpd-site</CODE> xdocs tree.<BR>
- <CODE><B>$ cd httpd-site/xdocs/</B></CODE>
- <P>
- <LI> Edit the <A HREF="http://httpd.apache.org/"><CODE>index.xml</CODE></A>
- page from the <CODE>httpd-site</CODE> CVS tree as required:<BR>
- <CODE><B>$ vi index.xml</B></CODE><BR>
- <P>
- <LI> Commit the changes:<BR>
- <CODE><B>$ cd ..<BR>
- <CODE><B>$ ./build.sh # Check result before continuing<BR>
- <CODE><B>$ cvs commit</B></CODE><BR>
- <P>
- <LI> Update the checked-out versions of the <CODE>httpd-dist</CODE> documents
- for the web server:<BR>
- <CODE><B>$ umask 002</B></CODE><BR>
- <CODE><B>$ cd /www/www.apache.org/dist/httpd/</B></CODE><BR>
- <CODE><B>$ cvs update -dP</B></CODE>
- <P>
- <LI> Create an empty directory for future patches:<BR>
- <CODE><B>$ mkdir patches/apply_to_1.<EM>X.Y</EM></B></CODE>
- <P>
- <LI> Update the checked-out version of the <CODE>httpd-site index.html</CODE>
- page for the web server:<BR>
- <CODE><B>$ umask 002</B></CODE><BR>
- <CODE><B>$ cd /www/httpd.apache.org/</B></CODE><BR>
- <CODE><B>$ cvs update -dP</B></CODE>
- <P>
- <LI>At this point, the web-sites reflect the existance of the new release.
- <p>
- As it is going to be some 24hrs before any announcement goes out
- (to make sure that the mirror's have at least a chance of grabbing
- a copy) this is also the right time to mail dev@httpd.apache.org
- and ask people to upload and move into position any
- <a href="binaries.html">binaries</a> they have build and vetted.
-</OL>
-
-<P>
-
-<h2>Announcing a New Release</h2>
-<p>Once a release is built (<a href="#tarball">see below</a>),
-it is time to announce it to the world.
+ <a href="http://www.apache.org/dist/httpd/"><code>./dist</code></a>
+ subdirectory). The <code>Announcement.*</code> files should be based on
+ the <code>Announcement</code> file in the tagged CVS tree. For Apache
+ 2.0, <code>Announcement</code> should be replaced with
+ <code>Announcement2</code>:<br />
+ <code><b>$ vi README.html HEADER.html Announcement.html Announcement.txt
+ .htaccess</b></code><br />
+ </li>
+ <li>Commit the changes:<br />
+ <code><b>$ cvs commit README.html HEADER.html Announcement.html Announcement.txt .htaccess</b></code><br />
+ <code><b>$ cd ../..</b></code>
+ </li>
+ <li>Checkout the <a href="http://httpd.apache.org/">httpd site</a> if needed into a scratch directory:<br />
+ <code><b>$ cvs -d cvs.apache.org:/home/cvs checkout httpd-site</b></code>
+ </li>
+ <li>cd into the <code>httpd-site</code> xdocs tree.<br />
+ <code><b>$ cd httpd-site/xdocs/</b></code>
+ </li>
+ <li>Edit the <a href="http://httpd.apache.org/"><code>index.xml</code></a>
+ page from the <code>httpd-site</code> CVS tree as required:<br />
+ <code><b>$ vi index.xml</b></code><br />
+ </li>
+ <li>Commit the changes:<br />
+ <code><b>$ cd ..</b></code><br />
+ <code><b>$ ./build.sh # Check result before continuing</b></code><br />
+ <code><b>$ cvs commit</b></code><br />
+ </li>
+ <li>Update the checked-out versions of the <code>httpd-dist</code> documents
+ for the web server:<br />
+ <code><b>$ umask 002</b></code><br />
+ <code><b>$ cd /www/www.apache.org/dist/httpd/</b></code><br />
+ <code><b>$ cvs update -dP</b></code>
+ </li>
+ <li>Create an empty directory for future patches:<br />
+ <code><b>$ mkdir patches/apply_to_1.<em>X.Y</em></b></code>
+ </li>
+ <li>Update the checked-out version of the <code>httpd-site index.html</code>
+ page for the web server:<br />
+ <code><b>$ umask 002</b></code><br />
+ <code><b>$ cd /www/httpd.apache.org/</b></code><br />
+ <code><b>$ cvs update -dP</b></code>
+ </li>
+</ol>
+<p>At this point, the web-sites reflect the existance of the new release.</p>
+<p>As it is going to be some 24hrs before any announcement goes out
+ (to make sure that the mirror's have at least a chance of grabbing
+ a copy) this is also the right time to mail dev@httpd.apache.org
+ and ask people to upload and move into position any
+ <a href="binaries.html">binaries</a> they have build and vetted.
+</p>
+ </blockquote>
+ </td></tr>
+</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="win32"><strong>How to build an Apache Windows release</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p>See <a href="how-to-release-win32">how to build a release of Apache
+for Windows</a>.</p>
+ </blockquote>
+ </td></tr>
+</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="announce"><strong>Announcing a New Release</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p>Once a release is <a href="#unix">built</a> and
+ <a href="#release">released</a>, it is time to announce it to the world.
+</p>
<ol>
- <hr>
- <b>[ Grab the prepared Announcement ]</b><br>
- <p>
- <li>You can grab either the <CODE>Announcement</CODE> file in the tagged tree, or the <CODE>Announcement.txt</CODE> file from the web-site.<br>
- <p>
- <hr>
- <b>[ Posting the Announcement ]</b><br>
- <p>
- <li>Once the tarball is built, give the mirrors a good 24 hours
- to get up to sync. This is really important if this this
- a final (i.e.: non-beta) release.
- <p>
- <li>Now, <code>Announcement</code> should be
+ <li>Grab the prepared Announcement:<br />
+ <p>You can grab either the <code>Announcement</code> file in the tagged
+ tree, or the <code>Announcement.txt</code> file from the
+ web-site.</p>
+ </li>
+ <li>Post the Announcement:<br />
+ <p>Once the tarball is built, give the mirrors a good 24 hours
+ to get up to sync. This is really important if this this
+ a final (i.e.: non-beta) release.</p>
+ </li>
+ <li>Now, <code>Announcement</code> should be
posted to the following places:
- <ul>
- <li>Unmoderated UseNet newsgroups (should be crossposted)
- <ul>
- <li><code>comp.infosystems.www.servers.unix</code>
- <li><code>comp.infosystems.www.servers.ms-windows</code>
- <li><code>comp.infosystems.www.servers.misc</code>
- <li><code>de.comm.infosystems.www.servers</code>
- </ul>
- <li>Moderated UseNet newsgroups (do <b>not</b> crosspost)
- <ul>
- <li><code>comp.infosystems.www.announce</code>
- </ul>
- <li>Mailing Lists
- <ul>
- <li><code>announce@apache.org</code>
- <li><code>ml-apache@unix-ag.org</code>
- </ul>
- </ul>
- <p>
+ <ul>
+ <li>Unmoderated UseNet newsgroups (should be crossposted)
+ <ul>
+ <li><code>comp.infosystems.www.servers.unix</code></li>
+ <li><code>comp.infosystems.www.servers.ms-windows</code></li>
+ <li><code>comp.infosystems.www.servers.misc</code></li>
+ <li><code>de.comm.infosystems.www.servers</code></li>
+ </ul>
+ </li>
+ <li>Moderated UseNet newsgroups (do <b>not</b> crosspost)
+ <ul>
+ <li><code>comp.infosystems.www.announce</code></li>
+ </ul>
+ </li>
+ <li>Mailing Lists
+ <ul>
+ <li><code>announce@apache.org</code></li>
+ <li><code>ml-apache@unix-ag.org</code></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
<li>Make sure that <code>Announcement.txt</code> and
- <code>Announcement.html</code> in <code>apache-site</code>
- in the <code>dist</code> directory are updated to include
- these changes.
- <p>
- <li>Bask in the glow
+ <code>Announcement.html</code> in <code>apache-site</code>
+ in the <code>dist</code> directory are updated to include
+ these changes.
+ </li>
+ <li>Bask in the glow</li>
</ol>
-<p>
-<P><BR>
-<H2>How to build an Apache Windows release</H2>
-
-See <A HREF="how-to-release-win32">how to build a release of Apache
-for Windows</A>.
-
-<!--#include virtual="footer.html" -->
-
-</BODY>
-</HTML>
+ </blockquote>
+ </td></tr>
+</table>
+ </td>
+ </tr>
+ <!-- FOOTER -->
+ <tr><td colspan="2"><hr noshade="noshade" size="1"/></td></tr>
+ <tr><td colspan="2" align="center">
+ <font size="-1">
+ <em>Copyright © 1999-2001, The Apache Software Foundation</em>
+ </font>
+ </td>
+ </tr>
+ </table>
+ </body>
+</html>
1.4 +3 -3 httpd-site/docs/dev/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/dev/index.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.html 2001/11/22 05:02:32 1.3
+++ index.html 2001/11/24 07:15:54 1.4
@@ -85,7 +85,7 @@
<li><a href="http://httpd.apache.org/mail/">Archives</a> of the Apache
HTTPD-related mailing lists.
</li>
- <li><a href="http://www.humanfactor.com/cgi-bin/cgi-delegate/apache-ML/nh/">Hypermail archive of new-httpd</a>.
+ <li><a href="http://marc.theaimsgroup.com/?l=apache-new-httpd">Archive of new-httpd</a>.
</li>
<li>How to contribute <a href="patches.html">code patches</a> to Apache.
</li>
@@ -149,8 +149,8 @@
</li>
<li>The <a href="todo.html">to-do list</a> of the Apache developers.
</li>
- <li>Record of changes to the
- <a href="http://www.apache.org/websrc/viewcvs.cgi/apache-1.3/src/include/ap_mmn.h">module magic number</a>
+ <li>Record of changes to the module magic number <a href="http://cvs.apache.org/viewcvs.cgi/apache-1.3/src/include/ap_mmn.h">1.3</a>
+ <a href="http://cvs.apache.org/viewcvs.cgi/httpd-2.0/include/ap_mmn.h">2.0</a>
<br />
</li>
</ul>