martin 98/10/06 13:33:43
Modified: . how-to-release.html
Log:
Add pointer to copies of Announcement
Revision Changes Path
1.48 +49 -18 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.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- how-to-release.html 1998/10/06 15:05:29 1.47
+++ how-to-release.html 1998/10/06 20:33:42 1.48
@@ -41,8 +41,8 @@
<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 <STRONG>before</STRONG> the Release is actually built. So
-we describe these steps at the beginning.
+should be composed and committed <STRONG>before</STRONG> the
+Release is actually built. So we describe these steps at the beginning.
<OL>
<HR>
@@ -55,12 +55,16 @@
release. For example, the Release Version should reflect
what is actually being announced. Also, the key enhancements
of the Release should be noted.<BR>
- <CODE><STRONG>$ cvs checkout apache-1.X</STRONG></CODE><BR>
+ <CODE><STRONG>$ cvs checkout apache-1.X/Announcement</STRONG></CODE><BR>
<CODE><STRONG>$ cd apache-1.X</STRONG></CODE><BR>
<CODE><STRONG>$ vi Announcement</STRONG></CODE><BR>
<CODE><STRONG>$ cvs commit Announcement</STRONG></CODE><BR>
<CODE><STRONG>$ cd ..</STRONG></CODE><BR>
<CODE><STRONG>$ cvs release -d apache-1.X</STRONG></CODE>
+ <P>
+ <STRONG>Note:</STRONG> This document is also present in the
+ <CODE>apache-site/dist/</CODE> directory, both in HTML and plain
+ text form. You may want to create one version out of the other.
<P>
<HR>
<STRONG>[ Building the source release ]</STRONG><BR>
@@ -112,9 +116,10 @@
will be noted.
<P><FONT COLOR="red">Important:</FONT> Once tagged and the tarball
-is rolled, there is no going back. If there are problems with
-the tarball, the version number (either the rev-level or beta-level)
-<EM>must</EM> be bumped resulting in a new tag, tarball and release.
+is rolled, there is <STRONG>no going back</STRONG>. If there are
+problems with the tarball, the version number (either the rev-level
+or beta-level) <EM>must</EM> be bumped resulting in a new tag,
+tarball and release.
<OL>
<HR>
@@ -139,7 +144,7 @@
edit <SAMP>src/os/win32/registry.c</SAMP> and change the
<CODE>VERSION</CODE> from <CODE>"1.X.Y dev"</CODE> to the
string <CODE>"1.X.Y"</CODE>.<BR> Additionally make sure the
- Configure scripts version knowledge for the
+ Configure script's 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.
@@ -149,9 +154,14 @@
<CODE><STRONG>$ vi src/Configure</STRONG></CODE><BR>
<CODE><STRONG>$ cvs commit src/include/httpd.h src/os/win32/registry.c
src/Configure</STRONG></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
+ ``<CODE>pgp -kxa</CODE>'' command, add them to the
+ <CODE>KEYS</CODE> file and commit it before tagging.
+<P>
<LI> Tag the sources for this release:<BR>
(<EM>note: be sure to tag the whole thing, not just
<CODE>src</CODE></EM>!)<BR>
- <CODE><STRONG>$ cvs tag APACHE_1_X_Y .</STRONG></CODE>
+ <CODE><STRONG>$ cvs tag APACHE_1_X_Y</STRONG></CODE>
<P>
<HR>
<STRONG>[ For all releases ]</STRONG><BR>
@@ -228,7 +238,8 @@
required. We still need the CVS tree, see below)<BR>
<CODE><STRONG>$ rm -fr apache_1.X.Y</STRONG></CODE>
<P>
-<LI> Make the tarball available for testing purposes:
(http://dev.apache.org/dist/)<BR>
+<LI> Make the tarball available for testing purposes
+ (in <A
HREF="http://dev.apache.org/dist/";>http://dev.apache.org/dist/</A>):<BR>
<CODE><STRONG>$ chmod 664 CHANGES apache_1.X.Y.tar.*</STRONG></CODE><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>
@@ -253,9 +264,9 @@
<CODE>APACHE_RELEASE</CODE> to <CODE>1XX(YY+1)01</CODE>.<BR>
In the <CODE>VERSION</CODE> macro in
<SAMP>src/os/win32/registry.c</SAMP>, increase the version
- number and re-insert the "dev" suffix (change the string
- ``<CODE>1.X.Y</CODE>'' to ``<CODE>1.X.(Y+1) dev</CODE>''; note
- the SPACE character instrad of the hyphen).<BR>
+ number and re-insert the `` dev'' suffix (change the string
+ ``<CODE>1.X.Y</CODE>'' to ``<CODE>1.X.(Y+1) dev</CODE>''; note
+ the SPACE character instead of the hyphen).<BR>
<CODE><STRONG>$ vi src/include/httpd.h
src/os/win32/registry.c</STRONG></CODE><BR>
<CODE><STRONG>$ cvs commit src/include/httpd.h
src/os/win32/registry.c</STRONG></CODE><BR>
<CODE><STRONG>$ cd ..</STRONG></CODE><BR>
@@ -275,7 +286,8 @@
these instructions until the group really approves the tarball !</EM>
<P>
-<LI> Make the distribution available: (http://www.apache.org/dist/)<BR>
+<LI> Make the distribution available
+ (in <A
HREF="http://www.apache.org/dist/";>http://www.apache.org/dist/</A>):<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>
@@ -294,22 +306,41 @@
<LI> cd into the <CODE>apache-site</CODE> CVS tree.<BR>
<CODE><STRONG>$ cd apache-site</STRONG></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><STRONG>$ vi dist/README.html</STRONG></CODE><BR>
+<LI> Edit the files
+ <A
HREF="http://www.apache.org/dist/README.html";><CODE>README.html</CODE></A> as
well as
+ <A
HREF="http://www.apache.org/dist/Announcement.html";><CODE>Announcement.html</CODE></A>
and its plaintext equivalent
+ <A
HREF="http://www.apache.org/dist/Announcement.txt";><CODE>Announcement.txt</CODE></A>
plus the
+ <A
HREF="http://www.apache.org/dist/.htaccess";><CODE>.htaccess</CODE></A> file
(which defines the
+ <CODE>AddDescription</CODE> comments)
+ from the <CODE>apache-site</CODE> CVS tree
+ as required (all in the
+ <A HREF="http://www.apache.org/dist/";><CODE>./dist</CODE></A>
+ subdirectory):<BR>
+ <CODE><STRONG>$ vi dist/README.html \<BR>
+ dist/Announcement.html \<BR>
+ dist/Announcement.txt \<BR>
+ dist/.htaccess</STRONG></CODE><BR>
<P>
<LI> Edit the Apache <CODE>index.html</CODE> from <CODE>apache-site</CODE>
CVS tree as required:<BR>
<CODE><STRONG>$ vi index.html</STRONG></CODE><BR>
<P>
<LI> Commit the changes:<BR>
- <CODE><STRONG>$ cvs commit index.html dist/README.html</STRONG></CODE>
+ <CODE><STRONG>$ cvs commit index.html \<BR>
+ dist/README.html \<BR>
+ dist/Announcement.html \<BR>
+ dist/Announcement.txt \<BR>
+ dist/.htaccess</STRONG></CODE>
<P>
<LI> Update the checked-out versions of the <CODE>apache-site</CODE>
documents
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 dist/README.html</STRONG></CODE>
+ <CODE><STRONG>$ cvs update index.html \<BR>
+ dist/README.html \<BR>
+ dist/Announcement.html \<BR>
+ dist/Announcement.txt \<BR>
+ dist/.htaccess</STRONG></CODE>
<P>
<LI> Create an empty directory for future patches:<BR>
<CODE><STRONG>$ mkdir patches/apply_to_1.X.Y</STRONG></CODE>
