httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject svn commit: r1083575 - /httpd/site/trunk/xdocs/dev/how-to-release.xml
Date Sun, 20 Mar 2011 21:28:43 GMT
Author: wrowe
Date: Sun Mar 20 21:28:43 2011
New Revision: 1083575

URL: http://svn.apache.org/viewvc?rev=1083575&view=rev
Log:
Remove 1.3 references.

This file is still in need of MAJOR surgery.  CVS, anyone ;-?

Modified:
    httpd/site/trunk/xdocs/dev/how-to-release.xml

Modified: httpd/site/trunk/xdocs/dev/how-to-release.xml
URL: http://svn.apache.org/viewvc/httpd/site/trunk/xdocs/dev/how-to-release.xml?rev=1083575&r1=1083574&r2=1083575&view=diff
==============================================================================
--- httpd/site/trunk/xdocs/dev/how-to-release.xml [utf-8] (original)
+++ httpd/site/trunk/xdocs/dev/how-to-release.xml [utf-8] Sun Mar 20 21:28:43 2011
@@ -44,15 +44,7 @@ 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 />
+  <p>For Apache 2.<em>X</em>:<br />
      <code><b>$ cvs checkout -r APACHE_2_<em>X</em>_BRANCH -Pd httpd-2.<em>X</em></b>
httpd-2.0</code><br />
      <code><b>$ cd httpd-2.<i>X</i>/srclib</b></code><br
/>
      <code><b>$ cvs checkout apr apr-util</b></code><br />
@@ -81,18 +73,6 @@ tarball and release.</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>''.
@@ -123,28 +103,6 @@ tarball and release.</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
/>
-    <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 />
@@ -172,10 +130,6 @@ tarball and release.</p>
      &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 />
@@ -205,12 +159,6 @@ tarball and release.</p>
       </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>
@@ -256,27 +204,13 @@ tarball and release.</p>
      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
+    </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
/>
-     (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 />
@@ -284,13 +218,6 @@ tarball and release.</p>
      <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
@@ -391,8 +318,8 @@ these instructions until the group reall
 <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.
+   and ask people to upload and move into position any binaries 
+   they have build and vetted.
 </p>
 </section>
 



Mime
View raw message