You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@hyperreal.org on 1998/10/05 13:12:19 UTC
cvs commit: apache-devsite how-to-release.html
martin 98/10/05 04:12:19
Modified: . how-to-release.html
Log:
Fix some typos
Revision Changes Path
1.44 +14 -16 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.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- how-to-release.html 1998/09/21 19:54:44 1.43
+++ how-to-release.html 1998/10/05 11:12:19 1.44
@@ -141,9 +141,8 @@
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><BR>
<CODE><STRONG>$ vi src/Configure</STRONG></CODE><BR>
- <CODE><STRONG>$ cvs commit src/Configure</STRONG></CODE>
+ <CODE><STRONG>$ cvs commit src/include/httpd.h 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
@@ -188,7 +187,7 @@
<CODE><STRONG>$ find . -type d -name "CVS" -exec rm -rf {} \;</STRONG></CODE>
</UL>
<P>
-<LI> Expand the Service-Side-Include directives in the manual:<BR>
+<LI> Expand the Server-Side-Include directives in the manual:<BR>
<CODE><STRONG>$ cd htdocs/manual</STRONG></CODE><BR>
<CODE><STRONG>$ ./expand.pl</STRONG></CODE><BR>
<CODE><STRONG>$ rm ./expand.pl</STRONG></CODE><BR>
@@ -221,11 +220,8 @@
<P>
<LI> Remember the CHANGES file:<BR>
<CODE><STRONG>$ cp apache_1.X.Y/src/CHANGES .</STRONG></CODE>
-<P>
-<LI> Cleanup:<BR>
- <CODE><STRONG>$ rm -rf apache_1.X.Y</STRONG></CODE>
<P>
-<LI> Make the tarball available for testing purposes:<BR>
+<LI> Make the tarball available for testing purposes: (http://dev.apache.org/)<BR>
<CODE><STRONG>$ cp apache_1.X.Y.tar.gz /pub/httpd/dist</STRONG></CODE><BR>
<CODE><STRONG>$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist</STRONG></CODE><BR>
<CODE><STRONG>$ cp apache_1.X.Y.tar.Z /pub/httpd/dist</STRONG></CODE><BR>
@@ -242,20 +238,23 @@
<STRONG>[ Only for final releases, not for internal pre-releases ]</STRONG><BR>
<P>
<LI> cd back into the CVS tree location.<BR>
- <CODE><STRONG>$ cd apache-1.X</STRONG></CODE>
+ <CODE><STRONG>$ cd apache-1.X.Y</STRONG></CODE>
<P>
<LI> Change <CODE>SERVER_VERSION</CODE> in <CODE>src/include/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><STRONG>$ vi src/include/httpd.h</STRONG></CODE><BR>
- <CODE><STRONG>$ cvs commit src/include/httpd.h</STRONG></CODE>
+ <CODE><STRONG>$ cvs commit src/include/httpd.h</STRONG></CODE><BR>
+ <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
<P>
+<HR>
<LI> Cleanup:<BR>
- <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
- <CODE><STRONG>$ rm -rf apache-1.X</STRONG></CODE>
+ <CODE><STRONG>$ rm -rf apache-1.X.Y</STRONG></CODE>
<P>
<HR>
+<STRONG>[ Wait for group to test and approve the tarball ]</STRONG><BR>
+<HR>
<STRONG>[ Final release steps <U>after</U> the group has approved the tarball ]</STRONG><BR>
<P>
@@ -263,7 +262,7 @@
these instructions until the group really approves the tarball !</EM>
<P>
-<LI> Make the distribution available:<BR>
+<LI> Make the distribution available: (http://www.apache.org/)<BR>
<CODE><STRONG>$ cp CHANGES /pub/apache/dist</STRONG></CODE><BR>
<CODE><STRONG>$ cp apache_1.X.Y.tar.gz /pub/apache/dist</STRONG></CODE><BR>
<CODE><STRONG>$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist</STRONG></CODE><BR>
@@ -296,8 +295,7 @@
for the web server:<BR>
<CODE><STRONG>$ umask 002</STRONG></CODE><BR>
<CODE><STRONG>$ cd /pub/apache/</STRONG></CODE><BR>
- <CODE><STRONG>$ cvs update index.html</STRONG></CODE><BR>
- <CODE><STRONG>$ cvs update dist/index.html</STRONG></CODE>
+ <CODE><STRONG>$ cvs update index.html dist/README.html</STRONG></CODE>
<P>
<LI> Create an empty directory for future patches:<BR>
<CODE><STRONG>$ mkdir patches/apply_to_1.X.Y</STRONG></CODE>
@@ -349,14 +347,14 @@
<CODE><STRONG>> copy conf\httpd.conf-dist-win
\Apache_1.X.Y\httpd.conf-dist</STRONG></CODE><BR>
<CODE><STRONG>> copy conf\srm.conf-dist-win
- \Apache_1.X.Y\srm.conf</STRONG></CODE><BR>
+ \Apache_1.X.Y\srm.conf-dist</STRONG></CODE><BR>
<CODE><STRONG>> copy conf\mime.types
\Apache_1.X.Y\mime.types</STRONG></CODE><BR>
<CODE><STRONG>> copy conf\magic
\Apache_1.X.Y\magic</STRONG></CODE>
<P>
<LI>Move the HTML documents into place<BR>
- <CODE><STRONG>> copy htdocs \Apache_1.X.Y\htdocs</STRONG></CODE>
+ <CODE><STRONG>> copy htdocs \Apache_1.X.Y\htdocs /s</STRONG></CODE>
<P>
<LI>Copy the readme file<BR>
<CODE><STRONG>> copy README.NT \Apache_1.X.Y\readme.txt</STRONG></CODE>
Re: cvs commit: apache-devsite how-to-release.html
Posted by Marc Slemko <ma...@worldgate.com>.
On 5 Oct 1998 martin@hyperreal.org wrote:
> <P>
> <LI> Remember the CHANGES file:<BR>
> <CODE><STRONG>$ cp apache_1.X.Y/src/CHANGES .</STRONG></CODE>
Seeing this reminds me:
For some unknown reason at some time, someone decided that they should
get rid of CHANGES in /dist/ and just have CHANGES_1.3. This wasn't
discussed before being done, and I have no idea why it was done. It means
that the current documentation is out of date, since it clearly indicates
that it should be called CHANGES.
One of those inconsistencies should be fixed. Personally, the latest
CHANGES file has always been called CHANGES for a long time and I don't
see any reason to arbitrarily rename it.