httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerenkra...@apache.org
Subject cvs commit: httpd-site/xdocs/dev how-to-release.xml how-to-release.html
Date Sat, 24 Nov 2001 07:13:34 GMT
jerenkrantz    01/11/23 23:13:34

  Added:       xdocs/dev how-to-release.xml
  Removed:     xdocs/dev how-to-release.html
  Log:
  Convert the how-to-release page to XML format.
  
  Revision  Changes    Path
  1.1                  httpd-site/xdocs/dev/how-to-release.xml
  
  Index: how-to-release.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
    <properties>
      <author email="docs@httpd.apache.org">Documentation Group</author>
      <title>How to build a release of Apache</title>
    </properties>
  <body>
  
  <section><title>How to build a release of Apache</title>
  <p>
  Alexei Kosut &lt;akosut@apache.org&gt;<br />
  Ralf S. Engelschall &lt;rse@apache.org&gt;<br />
  Jim Jagielski &lt;jim@apache.org&gt;<br />
  Ken Coar &lt;coar@apache.org&gt;<br />
  Martin Kraemer &lt;martin@apache.org&gt;<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.</p>
  
  </section>
  
  <section id="unix"><title>How to build an Apache Unix release</title>
  
  <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>
  
  <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.</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>

       (two macros in the cvs configuration file
       <code><b>/home/cvs/CVSROOT/modules</b></code> do that for you).
    <p>
       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
        <code>httpd-dist</code> cvs module, both in HTML and plain
        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>
      <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.
   </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>
          <!-- 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>
   </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
       &gt; htdocs/manual/misc/FAQ.html</b></code>
   </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>
        </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 &lt;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
/>
       
      <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>
  	  <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
  	 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 />
       Finally, add a new line
           ``<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 />
       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>
      <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
  	 head of the <SAMP>CHANGES</SAMP> file for the
  	 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>
    </li>
  </ol>
  
  <p><b>Now wait for the group to test and approve the tarball.</b></p>
  </section>
  
  <section id="release"><title>Final release steps</title>
  <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>
   <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 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>
  </section>
  
  <section id="win32"><title>How to build an Apache Windows release</title>
  
  <p>See <a href="how-to-release-win32">how to build a release of Apache
  for Windows</a>.</p>
  </section>
  
  <section id="announce"><title>Announcing a New Release</title>
  
  <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>
    <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>
  	      <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.
   </li>
   <li>Bask in the glow</li>
  </ol>
  </section>
  
  </body>
  </document>
  
  
  

Mime
View raw message