You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rs...@hyperreal.org on 1998/04/14 16:40:58 UTC
cvs commit: apache-devsite how-to-release.html
rse 98/04/14 07:40:35
Modified: . how-to-release.html
Log:
Update the release steps.
Revision Changes Path
1.32 +48 -24 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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- how-to-release.html 1998/04/06 17:10:38 1.31
+++ how-to-release.html 1998/04/14 14:38:40 1.32
@@ -55,10 +55,12 @@
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.3</STRONG></CODE><BR>
- <CODE><STRONG>$ cd apache-1.3</STRONG></CODE><BR>
+ <CODE><STRONG>$ cvs checkout apache-1.X</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>
+ <CODE><STRONG>$ cvs commit Announcement</STRONG></CODE><BR>
+ <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
+ <CODE><STRONG>$ rm -rf apache-1.X</STRONG></CODE>
<P>
<HR>
<STRONG>[ Building the source release ]</STRONG><BR>
@@ -110,10 +112,10 @@
<OL>
<HR>
<LI> Checkout the Apache source if needed into a scratch directory:<BR>
- <CODE><STRONG>$ cvs checkout apache-1.3</STRONG></CODE>
+ <CODE><STRONG>$ cvs checkout apache-1.X</STRONG></CODE>
<P>
-<LI> cd into the <CODE>apache-1.3</CODE> CVS tree.<BR>
- <CODE><STRONG>$ cd apache-1.3</STRONG></CODE>
+<LI> cd into the <CODE>apache-1.X</CODE> CVS tree.<BR>
+ <CODE><STRONG>$ cd apache-1.X</STRONG></CODE>
<P>
<HR>
@@ -194,17 +196,20 @@
<CODE><STRONG>$ gunzip -c apache_1.X.Y.tar.gz | tar tvf -</STRONG></CODE><BR>
<CODE><STRONG>$ zcat apache_1.X.Y.tar.Z | tar tvf -</STRONG></CODE><BR>
<P>
-<LI> Cleanup:<BR>
- <CODE><STRONG>$ rm -rf apache_1.X.Y</STRONG></CODE>
-<P>
<LI> Sign the distribution files:<BR>
<CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.gz</STRONG></CODE><BR>
<CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.Z</STRONG></CODE><BR>
<UL>
<LI><FONT COLOR="red">Note:</FONT> Be sure your PGP key is already in the
- <CODE>KEYS</CODE> file!)<BR>
+ <CODE>KEYS</CODE> file!<BR>
</UL>
<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>
<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>
@@ -216,9 +221,25 @@
in <CODE>dev.apache.org</CODE> in the <CODE>/pub/httpd/dist</CODE>
directory.
</UL>
-
<P>
<HR>
+<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>
+<P>
+<LI> Change <CODE>SERVER_VERSION</CODE> in <CODE>src/main/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/main/httpd.h</STRONG></CODE><BR>
+ <CODE><STRONG>$ cvs commit src/main/httpd.h</STRONG></CODE>
+<P>
+<LI> Cleanup:<BR>
+ <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
+ <CODE><STRONG>$ rm -rf apache-1.X</STRONG></CODE>
+<P>
+<HR>
<STRONG>[ Final release steps <U>after</U> the group has approved the tarball ]</STRONG><BR>
<P>
@@ -227,6 +248,7 @@
<P>
<LI> Make the distribution available:<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>
<CODE><STRONG>$ cp apache_1.X.Y.tar.Z /pub/apache/dist</STRONG></CODE><BR>
@@ -247,25 +269,27 @@
<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>
- <CODE><STRONG>$ cvs commit dist/README.html</STRONG></CODE><BR>
+ <CODE><STRONG>$ cvs commit dist/README.html</STRONG></CODE>
<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>
- <CODE><STRONG>$ cvs commit index.html</STRONG></CODE><BR>
-<P>
-<HR>
-<STRONG>[ Only for final releases, not for internal pre-releases ]</STRONG><BR>
+ <CODE><STRONG>$ cvs commit index.html</STRONG></CODE>
<P>
-<LI> cd back into the <CODE>apache-1.3</CODE> CVS tree location.<BR>
- <CODE><STRONG>$ cd ../apache-1.3</STRONG></CODE>
+<LI> Update the checked-out versions of the <CODE>apache-site</CODE> documents
+ for the web server:<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>
+<P>
+<LI> Make an extracted version of the distribution available for
+ browsing by the user and for source-tree hyperlinks in
+ the Announcement posting:<BR>
+ <CODE><STRONG>$ cd dist</STRONG></CODE><BR>
+ <CODE><STRONG>$ gunzip <apache_1.X.Y.tar.gz | tar xvf -</STRONG></CODE>
<P>
-<LI> Change <CODE>SERVER_VERSION</CODE> in <CODE>src/main/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/main/httpd.h</STRONG></CODE><BR>
- <CODE><STRONG>$ cvs commit src/main/httpd.h</STRONG></CODE>
+<LI> Create an empty directory for future patches:<BR>
+ <CODE><STRONG>$ mkdir patches/apply_to_1.X.Y</STRONG></CODE>
</OL>
<P>
Re: cvs commit: apache-devsite how-to-release.html
Posted by Marc Slemko <ma...@worldgate.com>.
On 14 Apr 1998 rse@hyperreal.org wrote:
> rse 98/04/14 07:40:35
>
> Modified: . how-to-release.html
> Log:
> Update the release steps.
>
> Revision Changes Path
> 1.32 +48 -24 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.31
> retrieving revision 1.32
> diff -u -r1.31 -r1.32
> --- how-to-release.html 1998/04/06 17:10:38 1.31
> +++ how-to-release.html 1998/04/14 14:38:40 1.32
> @@ -55,10 +55,12 @@
> 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.3</STRONG></CODE><BR>
> - <CODE><STRONG>$ cd apache-1.3</STRONG></CODE><BR>
> + <CODE><STRONG>$ cvs checkout apache-1.X</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>
> + <CODE><STRONG>$ cvs commit Announcement</STRONG></CODE><BR>
> + <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
> + <CODE><STRONG>$ rm -rf apache-1.X</STRONG></CODE>
> <P>
> <HR>
> <STRONG>[ Building the source release ]</STRONG><BR>
> @@ -110,10 +112,10 @@
> <OL>
> <HR>
> <LI> Checkout the Apache source if needed into a scratch directory:<BR>
> - <CODE><STRONG>$ cvs checkout apache-1.3</STRONG></CODE>
> + <CODE><STRONG>$ cvs checkout apache-1.X</STRONG></CODE>
> <P>
> -<LI> cd into the <CODE>apache-1.3</CODE> CVS tree.<BR>
> - <CODE><STRONG>$ cd apache-1.3</STRONG></CODE>
> +<LI> cd into the <CODE>apache-1.X</CODE> CVS tree.<BR>
> + <CODE><STRONG>$ cd apache-1.X</STRONG></CODE>
> <P>
>
> <HR>
> @@ -194,17 +196,20 @@
> <CODE><STRONG>$ gunzip -c apache_1.X.Y.tar.gz | tar tvf -</STRONG></CODE><BR>
> <CODE><STRONG>$ zcat apache_1.X.Y.tar.Z | tar tvf -</STRONG></CODE><BR>
> <P>
> -<LI> Cleanup:<BR>
> - <CODE><STRONG>$ rm -rf apache_1.X.Y</STRONG></CODE>
> -<P>
> <LI> Sign the distribution files:<BR>
> <CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.gz</STRONG></CODE><BR>
> <CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.Z</STRONG></CODE><BR>
> <UL>
> <LI><FONT COLOR="red">Note:</FONT> Be sure your PGP key is already in the
> - <CODE>KEYS</CODE> file!)<BR>
> + <CODE>KEYS</CODE> file!<BR>
> </UL>
> <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>
Note that this is not the right thing to do for 1.2.x, since it goes
to CHANGES.1.2.
> <LI> Make the tarball available for testing purposes:<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>
> @@ -216,9 +221,25 @@
> in <CODE>dev.apache.org</CODE> in the <CODE>/pub/httpd/dist</CODE>
> directory.
> </UL>
> -
> <P>
> <HR>
> +<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>
Didn't you already tell them to remove it before? I'm not sure it is
necessary to tell people how to use rm...
> - <CODE><STRONG>$ cd ../apache-1.3</STRONG></CODE>
> +<LI> Update the checked-out versions of the <CODE>apache-site</CODE> documents
> + for the web server:<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>
It is worth adding a umask 002 in there.
> +<P>
> +<LI> Make an extracted version of the distribution available for
> + browsing by the user and for source-tree hyperlinks in
> + the Announcement posting:<BR>
> + <CODE><STRONG>$ cd dist</STRONG></CODE><BR>
> + <CODE><STRONG>$ gunzip <apache_1.X.Y.tar.gz | tar xvf -</STRONG></CODE>
I'm still not sure this is a good idea. I don't see that we gain
that much, we add a whole bunch of files for mirrors to pick up
(remember, a whole bunch of files can be a pain to transfer) and
we have the potential to really confuse people. Some people already
have trouble figuring out the name of the httpd binary in binary
distributions.