httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a..@locus.apache.org
Subject cvs commit: apache-devsite how-to-release.html
Date Mon, 05 Jun 2000 16:43:29 GMT
ask         00/06/05 09:43:28

  Modified:    .        how-to-release.html
  Log:
  no need to update registry.c anymore for windows.
  
  Revision  Changes    Path
  1.62      +3 -16     apache-devsite/how-to-release.html
  
  Index: how-to-release.html
  ===================================================================
  RCS file: /home/cvs/apache-devsite/how-to-release.html,v
  retrieving revision 1.61
  retrieving revision 1.62
  diff -u -r1.61 -r1.62
  --- how-to-release.html	2000/06/04 20:24:50	1.61
  +++ how-to-release.html	2000/06/05 16:43:27	1.62
  @@ -86,14 +86,8 @@
   	 The format is something like
   	 <CODE>printf("%d%02d%02d%d%02d", major, minor, bugfix, final,
   	 beta)</CODE>. <BR>
  -   (1.3.x only) Also update the Windows registry key:
  -	 edit <SAMP>src/os/win32/registry.c</SAMP> and change the
  -	 <CODE>VERSION</CODE> from <CODE>"1.<EM>X.Y</EM> dev"</CODE>
to the
  -	 string <CODE>"1.<EM>X.Y</EM>"</CODE>.
  -	 <BR>
        <CODE><B>$ vi src/include/httpd.h</B></CODE><BR>
  -     <CODE><B>$ vi src/os/win32/registry.c</B></CODE><BR>
  -     <CODE><B>$ cvs commit src/include/httpd.h src/os/win32/registry.c</B></CODE>
  +     <CODE><B>$ cvs commit src/include/httpd.h</B></CODE>
     <P>
    <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
  @@ -134,7 +128,7 @@
        <code><b>$ lynx -source http://www.apache.org/docs/misc/FAQ.html
        &gt; htdocs/manual/misc/FAQ.html</b></code>
     <p>
  - <LI> Create <CODE>src/Configuration</CODE> file:<BR>
  + <LI> Create <CODE>src/Configuration</CODE> file: (1.3.x only)<BR>
        <CODE><B>$ cp src/Configuration.tmpl src/Configuration</B></CODE>
     <P>
    <LI> Remove <CODE>STATUS</CODE>, <CODE>RULES.CVS</CODE>,

  @@ -225,12 +219,7 @@
   	 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>
  -     In the <CODE>VERSION</CODE> macro in
  -	 <SAMP>src/os/win32/registry.c</SAMP>, increase the version
  -	 number and re-insert the ``&nbsp;dev'' suffix (change the string
  -	 ``<CODE>1.<EM>X.Y</EM></CODE>'' to ``<CODE>1.<EM>X.(Y+1)</EM>&nbsp;dev</CODE>'';
note
  -	 the SPACE character instead of the hyphen).<BR>
  -     Additionally make sure that the Configure script's version
  +     (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>''
  @@ -240,11 +229,9 @@
   	 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>
  -	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/os/win32/registry.c \<BR>
   	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/Configure \<BR>
   	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/CHANGES</B></CODE><BR>
        <CODE><B>$ cvs commit src/include/httpd.h \<BR>
  -	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/os/win32/registry.c \<BR>
   	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/Configure \<BR>
   	     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src/CHANGES</B></CODE><BR>
        <CODE><B>$ cd ..</B></CODE><BR>
  
  
  

Mime
View raw message