[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-dev
Subject:    Re: T&R Procedure for 1.3?
From:       Jim Jagielski <jim () jaguNET ! com>
Date:       2007-07-31 13:17:04
Message-ID: B6F7C18B-AFF0-43D0-B9E3-B7AFEA94F374 () jaguNET ! com
[Download RAW message or body]

http://httpd.apache.org/dev/how-to-release.html is
kind of dated and yes is in need of an update, but
I've never bothered doing so (except for the last
1.3 release, I've been RM for 1.3 for the last several
years)....

The svn copy location however is

    https://svn.apache.org/repos/asf/httpd/httpd/tags/1.3/APACHE_1_3_MM

On Jul 25, 2007, at 10:30 PM, Sander Temme wrote:

> Folks,
>
> Before I perform my first Tag & Roll, I'm trying to familiarize  
> myself with the exact process.  Maybe I'm not looking in the right  
> places, or is the documentation actually a bit thin on the nuts and  
> bolts of the process?  Here's what I think should happen, gleaned  
> from the various pages and scripts:
>
> branches/1.3.x to tag version 1.3.MM:
>
> 1) Edit STATUS and src/include/httpd.h:
>
>    In STATUS, change version number 1.3.MM line to say "Tagged mm/ 
> dd/yyyy"
>
>    In httpd,h, remove "-dev" from SERVER_BASEREVISION define
>
>    Commit as revision rXXXXXX
>
> 2) svn copy -rXXXXXX https://svn.apache.org/repos/asf/httpd/httpd/ 
> branches/1.3.x \
>        https://svn.apache.org/repos/asf/httpd/httpd/tags/1.3.MM
>
>    This will be committed as rYYYYYY (likely rXXXXXX + 1 but that  
> is not certain)
>
> 3) Edit STATUS and src/include/httpd.h:
>
>    In STATUS, add line "1.3.(MM + 1): In development"
>
>    In httpd.h, change SERVER_BASEREVISION define to say "1.3.(MM +  
> 1)-dev
>    Also bump the APACHE_RELEASE define
>
>    Commit
>
> The previous I've inferred from the svn logs. Now I'm going by  
> http://httpd.apache.org/dev/how-to-release.html which points to  
> release.sh, but it looks like that only works for 2.x.  What of the  
> below still applies?
>
> 4) Export the source:
>
>    umask 022
>    svn export http://svn.apache.org/repos/asf/httpd/httpd/tags/ 
> 1.3.MM \
>        apache_1.3.MM
>
> 5) curl http://httpd.apache.org/docs/1.3/misc/FAQ.html \
>      > htdocs/manual/misc/FAQ.html
>
> 6) cp src/Configuration.tmpl src/Configuration
>
> 7) Remove various dev-only files:
>
>    rm -f STATUS RULES.CVS src/INDENT htdocs/manual/misc./FAQ-*.html
>    find . -name ".cvsignore" -exec rm {} \;
>    find . -type d -name "test" -exec rm -Rf {} \;
>    find . -type d -name ".svn" -exec rm -Rf {} \;
>
> 8) Expand the Server-Side-Include directives in the manual:
>
>    cd htdocs/manual
>    ./expand.pl
>
> 9) Roll the tarballs:
>
>    tar -czf apache_1.3.MM.tar.gz apache_1.3.MM
>    tar -cf apache_1.3.MM.tar apache_1.3.MM
>    compress apache_1.3.MM.tar
>
> 10) Test the tarballs for untarrability
>
>     tar -tzf apache_1.3.MM.tar.gz
>
>     unzompress < apache_1.3.MM.tar.Z | tar -tf -
>
> 12) PGP sign the tarballs
>
>     gpg -sba apache_1.3.MM.tar.gz
>     gpg -sba apache_1.3.MM.tar.Z
>
> 13) Test the signatures
>
>     gpg --verify apache_1.3.MM.tar.gz.asc
>     gpg --verify apache_1.3.MM.tar.Z.asc
>
> 14) Pull out the CHANGES file for upload to the web
>
>     cp apache_1.3.MM/src/CHANGES ./CHANGES_1.3
>
> 15) Upload the tarballs to the website
>
>     scp apache_1.3.MM.tar.gz apache_1.3.MM.tar.Z \
>         apache_1.3.MM.tar.gz.asc apache_1.3.MM.tar.Z.asc  \
>         CHANGES_1.3 people.apache.org:
> 16) Move in place:
>
>     ssh people.apache.org
>     umask 002
>     mv apache_1.3.MM.tar.gz apache_1.3.MM.tar.Z \
>         apache_1.3.MM.tar.gz.asc apache_1.3.MM.tar.Z.asc  \
>         CHANGES_1.3 /www/httpd.apache.org/dev/dist
>
>     They should show up group-writable.  If not, you umask was off,  
> do correct.
>     If the mv doesn't work, you're not in the right unix group.   
> Have infra
>     correct.
>
> 17) Wait patiently for rsync, avoid bitching to infra at all costs.
>
> 18) Mail dev@httpd.a.o, testers@httpd.a.o with a [VOTE] e-mail  
> copied from an
>     earlier release effort lovingly archived on mail-archives.a.o/ 
> mod_mbox.
>     NOTE it'd be highly desirable if all branches' tarballs were  
> announced for
>     testing in one such e-mail
>
> 19) Sit back and watch the votes roll in
>
> Comments?  Critique?  I'll be happy to update how-to-release.html  
> accordingly.
>
> S.
>
> -- 
> sander@temme.net              http://www.temme.net/sander/
> PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF
>

[prev in list] [next in list] [prev in thread] [next in thread]