rse 98/07/21 03:28:45
Modified: . how-to-release.html
Log:
Make sure the V.R.P triple for SHARED_CORE is correct when releasing.
Revision Changes Path
1.42 +7 -1 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.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- how-to-release.html 1998/06/07 01:49:58 1.41
+++ how-to-release.html 1998/07/21 10:28:43 1.42
@@ -135,9 +135,15 @@
``<CODE>1XXYYZZ</CODE>'' to ``<CODE>1XXYY<STRONG>99</STRONG></CODE>''.
The format is something like
<CODE>printf("%d%02d%02d%02d", major, minor, bugfix,
- betaseq)</CODE>.<BR>
+ betaseq)</CODE>. Additionally make sure the Configure scripts version
+ knowledge for the <CODE>SHARED_CORE</CODE> reflects the correct
+ version.revision.patchlevel triple. Look for the line ``<CODE>V=1 R=3
+ P=2</CODE>'' inside <CODE>src/Configure</CODE> and adjust it
accordingly.
+ <BR>
<CODE><STRONG>$ vi src/include/httpd.h</STRONG></CODE><BR>
<CODE><STRONG>$ cvs commit src/include/httpd.h</STRONG></CODE>
+ <CODE><STRONG>$ vi src/Configure</STRONG></CODE><BR>
+ <CODE><STRONG>$ cvs commit src/Configure</STRONG></CODE>
<P>
If the release is going from beta to non-beta, or non-beta to a
beta, also update the Windows registry key release. See
