Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 23453 invoked by uid 6000); 14 Apr 1998 16:04:01 -0000 Received: (qmail 23327 invoked from network); 14 Apr 1998 16:03:54 -0000 Received: from valis.worldgate.com (marcs@198.161.84.2) by taz.hyperreal.org with SMTP; 14 Apr 1998 16:03:54 -0000 Received: from localhost (marcs@localhost) by valis.worldgate.com (8.8.7/8.8.7) with SMTP id KAA26471 for ; Tue, 14 Apr 1998 10:03:53 -0600 (MDT) Date: Tue, 14 Apr 1998 10:03:53 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: Re: cvs commit: apache-devsite how-to-release.html In-Reply-To: <19980414144058.4967.qmail@hyperreal.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org 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.
> - $ cvs checkout apache-1.3
> - $ cd apache-1.3
> + $ cvs checkout apache-1.X
> + $ cd apache-1.X
> $ vi Announcement
> - $ cvs commit Announcement > + $ cvs commit Announcement
> + $ cd ..
> + $ rm -rf apache-1.X >

> [ Building the source release ]
> @@ -110,10 +112,10 @@ >

Checkout the Apache source if needed into a scratch directory:
> - $ cvs checkout apache-1.3 > + $ cvs checkout apache-1.X >
> -
cd into the apache-1.3 CVS tree.
> - $ cd apache-1.3 > +
cd into the apache-1.X CVS tree.
> + $ cd apache-1.X >
> >
> @@ -194,17 +196,20 @@ > $ gunzip -c apache_1.X.Y.tar.gz | tar tvf -
> $ zcat apache_1.X.Y.tar.Z | tar tvf -
>
> -
Cleanup:
> - $ rm -rf apache_1.X.Y > -
>
Sign the distribution files:
> $ pgp -sba apache_1.X.Y.tar.gz
> $ pgp -sba apache_1.X.Y.tar.Z
>
- Note: Be sure your PGP key is already in the > - KEYS file!)
  > + KEYS file!
  >
>
> +
Remember the CHANGES file:
> + $ cp apache_1.X.Y/src/CHANGES . > +
> +
Cleanup:
> + $ rm -rf apache_1.X.Y > +
Note that this is not the right thing to do for 1.2.x, since it goes to CHANGES.1.2. >
Make the tarball available for testing purposes:
> $ cp apache_1.X.Y.tar.gz /pub/httpd/dist
> $ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist
> @@ -216,9 +221,25 @@ > in dev.apache.org in the /pub/httpd/dist > directory. > > - >
>
> +[ Only for final releases, not for internal pre-releases ]
> +
> +
cd back into the CVS tree location.
> + $ cd apache-1.X Didn't you already tell them to remove it before? I'm not sure it is necessary to tell people how to use rm... > - $ cd ../apache-1.3 > +
Update the checked-out versions of the apache-site documents > + for the web server:
> + $ cd /pub/apache/
> + $ cvs update index.html
> + $ cvs update dist/index.html It is worth adding a umask 002 in there. > +
> +
Make an extracted version of the distribution available for > + browsing by the user and for source-tree hyperlinks in > + the Announcement posting:
> + $ cd dist
> + $ gunzip <apache_1.X.Y.tar.gz | tar xvf - 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.