jim 97/10/20 14:09:21
Modified: . how-to-release.html index.html Log: Document various changes: o apache -> apachen o some remote considerations if rolling the tarball o some HTML cleanup Revision Changes Path 1.19 +78 -40 apache-devsite/how-to-release.html Index: how-to-release.html =================================================================== RCS file: /export/home/cvs/apache-devsite/how-to-release.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- how-to-release.html 1997/10/18 15:53:38 1.18 +++ how-to-release.html 1997/10/20 21:09:20 1.19 @@ -3,6 +3,7 @@ <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" @@ -16,9 +17,9 @@ <h1>Announcing a New Release</h1> -<p>Once a release is built, it is time to announce it to the -world. Ideally, the Announcement should be composed before the -Release is actually built. +<p>Once a release is built (<A HREF="#tarball">see below</A>), +it is time to announce it to the world. Ideally, the Announcement +should be composed before the Release is actually built. <ol> <hr> @@ -37,7 +38,8 @@ <b>[ Posting the Announcement ]</b><br> <p> - <li>First, build the source release (see below) if not already done. + <li>First, build the source release (<A HREF="#tarball">see below</A>) + if not already done. <li>Once built, <code>Announcement</code> should be posted to the following places: <ul> @@ -64,24 +66,31 @@ <hr> -<H1>How to build a release of Apache</H1> - -<P>First, use ssh to login to your dev.apache.org account and cd to a scratch -directory. +<H1><A NAME="tarball">How to build a release of Apache</A></H1> +<P><FONT COLOR="red">Note:</FONT> The below assumes that you are +using <code>ssh</code> to login to your <code>dev.apache.org</code> +account. If you are "rolling the tarball" remotely, the differences +will be noted. <OL> <HR> +<LI> Checkout the Apache source if needed into a scratch directory:<br> + <code><b>$ cvs checkout apachen</b></code> +<P> +<LI> cd into the <code>apachen</code> CVS tree.<br> + <code><b>$ cd apachen</b></code> +<P> <b>[ Only for final releases, not for internal pre-releases ]</b><br> <P> -<LI> Change <code>SERVER_VERSION</code> in <tt>src/httpd.h</tt> +<LI> Change <code>SERVER_VERSION</code> in <tt>src/main/httpd.h</tt> from ``<code>Apache/1.X.Y-dev</code>'' to ``<code>Apache/1.X.Y</code>''. Then also change <code>APACHE_RELEASE</code> in same file from ``<code>1XXYYZZ</code>'' to ``<code>1XXYY99</code>''. The format is something like <code>printf("%d%02d%02d%02d", major, minor, bugfix, betaseq)</code>.<br> - <code><b>$ vi src/httpd.h</b></code><br> - <code><b>$ cvs commit src/httpd.h</b></code> + <code><b>$ vi src/main/httpd.h</b></code><br> + <code><b>$ cvs commit src/main/httpd.h</b></code> <P> <LI> Tag the sources for this release:<br> (<i>note: be sure to tag the whole thing, not just <code>src</code></i>!)<br> @@ -92,9 +101,19 @@ <P> <P> <LI> Make an export version of the distribution:<br> + <code><b>$ cd ..</b></code><br> <code><b>$ umask 022</b></code><br> - <code><b>$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache</b></code><br> - <code><b>$ cd apache_1.X.Y</b></code> + <code><b>$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apachen</b></code><br> + <code><b>$ cd apache_1.X.Y</b></code><br> + <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_X_Y -d apache_1.X.Y apachen</b></code><br> + <code><b>$ cd apache_1.X.Y</b></code><br> + </UL> <P> <LI> Create <code>src/Configuration</code> file:<br> <code><b>$ cp src/Configuration.tmpl src/Configuration</b></code> @@ -102,6 +121,12 @@ <LI> Remove <code>RULES.CVS</code> file and various <code>.cvsignore</code> files:<br> <code><b>$ rm RULES.CVS</b></code><br> <code><b>$ find . -name ".cvsignore" -exec rm {} \;</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> Add an empty <code>logs/</code> directory:<br> <code><b>$ mkdir logs</b></code> @@ -138,27 +163,40 @@ <code><b>$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist</b></code><br> <code><b>$ cp apache_1.X.Y.tar.Z /pub/apache/dist</b></code><br> <code><b>$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist</b></code><br> -<P> -<LI> Adjust the README.html file as required:<br> - <li>Edit <code>README.html</code> from <code>apache-site</code> CVS tree - (it's in the <code>./dist</code> subdirectory) - <li><code>commit</code> the changes -<P> -<LI> Adjust the Apache index.html file as required:<br> - <ol> - <li>Edit <code>index.html</code> from <code>apache-site</code> CVS tree - <li><code>commit</code> the changes - </ol> + <UL> + <LI><FONT COLOR="red">Note:</FONT> If rolling the tarball + remotely, you should use <code>scp</code> to place them + in <code>dev.apache.org</code> in the <code>/pub/apache/dist</code> + directory. + </UL> +<P> +<LI> Checkout the Apache site if needed into a scratch directory:<br> + <code><b>$ cvs checkout apache-site</b></code> +<P> +<LI> cd into the <code>apache-site</code> CVS tree.<br> + <code><b>$ cd apache-site</b></code> +<P> +<LI> Edit <code>README.html</code> from <code>apache-site</code> CVS tree + (it's in the <code>./dist</code> subdirectory) as required:<br> + <code><b>$ vi dist/README.html</b></code><br> + <code><b>$ cvs commit dist/README.html</b></code><br> +<P> +<LI> Edit the Apache <code>index.html</code> from <code>apache-site</code> + CVS tree as required:<br> + <code><b>$ cvs commit index.html</b></code><br> <P> <HR> <b>[ Only for final releases, not for internal pre-releases ]</b><br> <P> -<LI> Change <code>SERVER_VERSION</code> in <code>src/httpd.h</code> +<LI> cd back into the <code>apachen</code> CVS tree location.<br> + <code><b>$ cd ../apachen</b></code> +<P> +<LI> Change <code>SERVER_VERSION</code> in <code>src/main/httpd.h</code> from ``<code>Apache/1.X.Y</code>'' to ``<code>Apache/1.X.(Y+1)-dev</code>'' and change <code>APACHE_RELEASE</code> to <code>1XX(YY+1)01</code>.<br> - <code><b>$ vi src/httpd.h</b></code><br> - <code><b>$ cvs commit src/httpd.h</b></code> + <code><b>$ vi src/main/httpd.h</b></code><br> + <code><b>$ cvs commit src/main/httpd.h</b></code> </OL> <P> @@ -171,7 +209,7 @@ <strong>Note:</strong> These instructions are temporary, until we have a working installation of InstallShield, which will eventually be used to distribute Apache for Windows. At that time, these instructions will be -replaced.</strong> +replaced. </blockquote> <ol> @@ -194,26 +232,26 @@ <b>[ Building a binary release ]</b><br> <p> <li>First, build the source release (see above). - <li>Compile and "install" a release version of Apache:Mbr> - <code><b>> nmake /f Makefile.nt _apacher</b></code><br> - <code><b>> nmake /f Makefile.nt installr</b></code> + <li>Compile and "install" a release version of Apache:<br> + <code><b>> nmake /f Makefile.nt _apacher</b></code><br> + <code><b>> nmake /f Makefile.nt installr</b></code> <li>Rename the directory<br> - <code><b>> move \Apache \Apache_1.X.Y</b></code> + <code><b>> move \Apache \Apache_1.X.Y</b></code> <li>Move the configuration files into the correct place<br> - <code><b>> copy conf\access.conf-dist-win + <code><b>> copy conf\access.conf-dist-win \Apache_1.X.Y\access.conf-dist</b></code><br> - <code><b>> copy conf\httpd.conf-dist-win + <code><b>> copy conf\httpd.conf-dist-win \Apache_1.X.Y\httpd.conf-dist</b></code><br> - <code><b>> copy conf\srm.conf-dist-win + <code><b>> copy conf\srm.conf-dist-win \Apache_1.X.Y\srm.conf</b></code><br> - <code><b>> copy conf\mime.types + <code><b>> copy conf\mime.types \Apache_1.X.Y\mime.types</b></code><br> - <code><b>> copy conf\magic + <code><b>> copy conf\magic \Apache_1.X.Y\magic</b></code> <li>Move the HTML documents into place<br> - <code><b>> copy htdocs \Apache_1.X.Y\htdocs</b></code> + <code><b>> copy htdocs \Apache_1.X.Y\htdocs</b></code> <li>Copy the readme file<br> - <code><b>> copy README.NT \Apache_1.X.Y\readme.txt</b></code> + <code><b>> copy README.NT \Apache_1.X.Y\readme.txt</b></code> <li>Install the Visual C++ runtime DLLs, wherever it is they need to go (???) <li>Create a zipfile of <code>\Apache_1.X.Y</code> named @@ -223,6 +261,6 @@ <!--#include virtual="footer.html" --> -Written by Alexei Kosut and Ralf S. Engelschall and Others +Written by Alexei Kosut and Ralf S. Engelschall and Jim Jagielski </BODY> </HTML> 1.10 +2 -2 apache-devsite/index.html Index: index.html =================================================================== RCS file: /export/home/cvs/apache-devsite/index.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- index.html 1997/08/23 04:42:25 1.9 +++ index.html 1997/10/20 21:09:21 1.10 @@ -62,10 +62,10 @@ >build binary distributions</A> (last modified on <!--#flastmod virtual="binaries.html" -->) </LI> - <LI>Instructions for constructing + <LI>Instructions for <A HREF="how-to-release" - >distribution kits</A> + >rolling the release tarballs</A> (last modified on <!--#flastmod virtual="how-to-release.html" -->) </LI> <LI>A <a href="binbuild.sh">shell script to build a binary release</a>.