cvs commit: apache-devsite how-to-release.html
jim 00/02/25 18:46:44 Modified:.how-to-release.html Log: Various changes, esp since the change to locus Revision ChangesPath 1.60 +192 -179 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.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- how-to-release.html 2000/02/25 15:40:44 1.59 +++ how-to-release.html 2000/02/26 02:46:44 1.60 @@ -38,80 +38,8 @@ P BR -H2Announcing a New Release/H2 + H2A NAME=tarballHow to build an Apache Unix release/A/H2 -POnce a release is built (A HREF=#tarballsee below/A), -it is time to announce it to the world. Ideally, the Announcement -should be composed and committed Bbefore/B the -Release is actually built. So we describe these steps at the beginning. - -OL -HR - - B[ Adjusting Announcement to taste ]/BBR - P - LIA prototype CODEAnnouncement/CODE is included in - the main CVS source tree. This file should be updated - to reflect the current state of affairs concerning the - release. For example, the Release Version should reflect - what is actually being announced. Also, the key enhancements - of the Release should be noted.BR - CODEB$ cvs checkout apache-1.EMX/EM/Announcement/B/CODEBR - CODEB$ cd apache-1.EMX/EM/B/CODEBR - CODEB$ vi Announcement/B/CODEBR - CODEB$ cvs commit Announcement/B/CODEBR - CODEB$ cd ../B/CODEBR - CODEB$ cvs release -d apache-1.EMX/EM/B/CODE - P - BNote:/B This document is also present in the - CODEapache-site/dist//CODE directory, both in HTML and plain - text form. You may want to create one version out of the other. - P - HR - B[ Building the source release ]/BBR - P - LIFirst, build the source release (A HREF=#tarballsee below/A) - if not already done. - P - HR - B[ Posting the Announcement ]/BBR - P - LIOnce the tarball is built, give the mirrors a good 24 hours - to get up to sync. This is really important if this this - a final (i.e.: non-beta) release. - LINow, CODEAnnouncement/CODE should be - posted to the following places: - UL -LIUnmoderated UseNet newsgroups (should be crossposted) - UL - LICODEcomp.infosystems.www.servers.unix/CODE - LICODEcomp.infosystems.www.servers.ms-windows/CODE - LICODEcomp.infosystems.www.servers.misc/CODE - LICODEde.comm.infosystems.www.servers/CODE - /UL -LIModerated UseNet newsgroups (do Bnot/B crosspost) - UL - LICODEcomp.infosystems.www.announce/CODE - /UL -LIMailing Lists - UL - LICODE[EMAIL PROTECTED]/CODE - LICODE[EMAIL PROTECTED]/CODE - /UL - /UL - P - LIMake sure that CODEAnnouncement.txt/CODE and - CODEAnnouncement.html/CODE in CODEapache-site/CODE - in the CODEdist/CODE directory are updated to include - these changes. - LIBask in the glow -/OL - -P -BR - -H2A NAME=tarballHow to build an Apache Unix release/A/H2 - PFONT COLOR=redNote:/FONT The below assumes that you are using CODEssh/CODE to login to your CODEdev.apache.org/CODE account. If you are rolling the tarball remotely, the differences @@ -124,25 +52,41 @@ tarball and release. OL -HR -LI Checkout the Apache source if needed into a scratch directory:BR + HR + LI Checkout the Apache source if needed into a scratch directory:BR CODEB$ cvs checkout apache-1.EMX/EM/B/CODE -P -LI cd into the CODEapache-1.EMX/EM/CODE CVS tree.BR + P + LI cd into the CODEapache-1.EMX/EM/CODE CVS tree.BR CODEB$ cd apache-1.EMX/EM/B/CODE -P - -HR -B[ Only for final releases, not for internal pre-releases ]/BBR -P -LI Change CODESERVER_VERSION/CODE in TTsrc/include/httpd.h/TT + Pb[ Adjusting Announcement to taste ]/bbr + LI + p +ul + liA prototype codeAnnouncement/code is included in + the main CVS source tree. This file should be updated + to reflect the current state of affairs concerning the + release. For example, the Release Version should reflect + what is actually being announced. Also, the key enhancements + of the Release should be noted.br + codeb$ vi Announcement/b/codebr + codeb$ cvs commit Announcement/b/codebr + p + bNote:/b This document is also present in the + codeapache-site/dist//code directory, both in HTML and plain + text form. You may want to create one version out of the other. + /ul + HR + B[ Only for final releases, not for internal pre-releases ]/BBR + P + LI Change CODESERVER_VERSION/CODE in TTsrc/include/httpd.h/TT from ``CODEApache/1.EMX.Y/EM-dev/CODE'' to
cvs commit: apache-devsite how-to-release.html
stoddard00/02/25 07:40:45 Modified:.how-to-release.html Log: Correct announce mailing list Revision ChangesPath 1.59 +1 -1 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.58 retrieving revision 1.59 diff -u -r1.58 -r1.59 --- how-to-release.html 1999/08/10 21:19:59 1.58 +++ how-to-release.html 2000/02/25 15:40:44 1.59 @@ -95,7 +95,7 @@ /UL LIMailing Lists UL - LICODE[EMAIL PROTECTED]/CODE + LICODE[EMAIL PROTECTED]/CODE LICODE[EMAIL PROTECTED]/CODE /UL /UL
cvs commit: apache-devsite how-to-release.html
coar99/08/10 08:37:17 Modified:.how-to-release.html Log: Fix the directory references to reflect Taz's new layout, and add the bit about fixing the FAQ -- expand.pl doesn't know how to deal with the QUERY_STRING aspects of the multi-part inclusion. Revision ChangesPath 1.57 +97 -87apache-devsite/how-to-release.html Index: how-to-release.html === RCS file: /home/cvs/apache-devsite/how-to-release.html,v retrieving revision 1.56 retrieving revision 1.57 diff -u -r1.56 -r1.57 --- how-to-release.html 1999/03/06 19:24:46 1.56 +++ how-to-release.html 1999/08/10 15:37:16 1.57 @@ -20,7 +20,8 @@ H1How to build a release of Apache/H1 Alexei Kosut lt;[EMAIL PROTECTED]gt;BR Ralf S. Engelschall lt;[EMAIL PROTECTED]gt;BR -Jim Jagielski lt;[EMAIL PROTECTED]gt; +Jim Jagielski lt;[EMAIL PROTECTED]gt;br +Ken Coar lt;[EMAIL PROTECTED]gt; /DIV BLOCKQUOTE @@ -41,13 +42,13 @@ POnce a release is built (A HREF=#tarballsee below/A), it is time to announce it to the world. Ideally, the Announcement -should be composed and committed STRONGbefore/STRONG the +should be composed and committed Bbefore/B the Release is actually built. So we describe these steps at the beginning. OL HR - STRONG[ Adjusting Announcement to taste ]/STRONGBR + B[ Adjusting Announcement to taste ]/BBR P LIA prototype CODEAnnouncement/CODE is included in the main CVS source tree. This file should be updated @@ -55,25 +56,25 @@ release. For example, the Release Version should reflect what is actually being announced. Also, the key enhancements of the Release should be noted.BR - CODESTRONG$ cvs checkout apache-1.EMX/EM/Announcement/STRONG/CODEBR - CODESTRONG$ cd apache-1.EMX/EM/STRONG/CODEBR - CODESTRONG$ vi Announcement/STRONG/CODEBR - CODESTRONG$ cvs commit Announcement/STRONG/CODEBR - CODESTRONG$ cd ../STRONG/CODEBR - CODESTRONG$ cvs release -d apache-1.EMX/EM/STRONG/CODE + CODEB$ cvs checkout apache-1.EMX/EM/Announcement/B/CODEBR + CODEB$ cd apache-1.EMX/EM/B/CODEBR + CODEB$ vi Announcement/B/CODEBR + CODEB$ cvs commit Announcement/B/CODEBR + CODEB$ cd ../B/CODEBR + CODEB$ cvs release -d apache-1.EMX/EM/B/CODE P - STRONGNote:/STRONG This document is also present in the + BNote:/B This document is also present in the CODEapache-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 ]/STRONGBR + B[ Building the source release ]/BBR P LIFirst, build the source release (A HREF=#tarballsee below/A) if not already done. P HR - STRONG[ Posting the Announcement ]/STRONGBR + B[ Posting the Announcement ]/BBR P LIOnce the tarball is built, give the mirrors a good 24 hours to get up to sync. This is really important if this this @@ -88,7 +89,7 @@ LICODEcomp.infosystems.www.servers.misc/CODE LICODEde.comm.infosystems.www.servers/CODE /UL -LIModerated UseNet newsgroups (do STRONGnot/STRONG crosspost) +LIModerated UseNet newsgroups (do Bnot/B crosspost) UL LICODEcomp.infosystems.www.announce/CODE /UL @@ -117,7 +118,7 @@ will be noted. PFONT COLOR=redImportant:/FONT Once tagged and the tarball -is rolled, there is STRONGno going back/STRONG. If there are +is rolled, there is Bno going back/B. If there are problems with the tarball, the version number (either the rev-level or beta-level) EMmust/EM be bumped resulting in a new tag, tarball and release. @@ -125,14 +126,14 @@ OL HR LI Checkout the Apache source if needed into a scratch directory:BR - CODESTRONG$ cvs checkout apache-1.EMX/EM/STRONG/CODE + CODEB$ cvs checkout apache-1.EMX/EM/B/CODE P LI cd into the CODEapache-1.EMX/EM/CODE CVS tree.BR - CODESTRONG$ cd apache-1.EMX/EM/STRONG/CODE + CODEB$ cd apache-1.EMX/EM/B/CODE P HR -STRONG[ Only for final releases, not for internal pre-releases ]/STRONGBR +B[ Only for final releases, not for internal pre-releases ]/BBR P LI Change CODESERVER_VERSION/CODE in TTsrc/include/httpd.h/TT from ``CODEApache/1.EMX.Y/EM-dev/CODE'' to @@ -146,9 +147,9 @@ CODEVERSION/CODE from CODE1.EMX.Y/EM dev/CODE to the string CODE1.EMX.Y/EM/CODE. BR - CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR - CODESTRONG$ vi src/os/win32/registry.c/STRONG/CODEBR - CODESTRONG$ cvs commit src/include/httpd.h src/os/win32/registry.c/STRONG/CODE + CODEB$ vi src/include/httpd.h/B/CODEBR + CODEB$ vi
cvs commit: apache-devsite how-to-release.html
coar99/08/10 14:20:02 Modified:.how-to-release.html Log: Oops. Caught by the dichotomy between the online and the repository paths.. Revision ChangesPath 1.58 +1 -1 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.57 retrieving revision 1.58 diff -u -r1.57 -r1.58 --- how-to-release.html 1999/08/10 15:37:16 1.57 +++ how-to-release.html 1999/08/10 21:19:59 1.58 @@ -185,7 +185,7 @@ p li Extract the FAQ as a single file, as it appears on the Web:br codeb$ lynx -source http://www.apache.org/docs/misc/FAQ.html - gt; htdocs/misc/FAQ.html/b/code + gt; htdocs/manual/misc/FAQ.html/b/code p LI Create CODEsrc/Configuration/CODE file:BR CODEB$ cp src/Configuration.tmpl src/Configuration/B/CODE
cvs commit: apache-devsite how-to-release.html
lars99/03/06 11:24:47 Modified:.how-to-release.html Log: Announce on german mailinglist, too. Revision ChangesPath 1.56 +1 -0 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.55 retrieving revision 1.56 diff -u -r1.55 -r1.56 --- how-to-release.html 1999/01/10 16:32:49 1.55 +++ how-to-release.html 1999/03/06 19:24:46 1.56 @@ -95,6 +95,7 @@ LIMailing Lists UL LICODE[EMAIL PROTECTED]/CODE + LICODE[EMAIL PROTECTED]/CODE /UL /UL P
cvs commit: apache-devsite how-to-release.html
fielding99/01/10 00:15:52 Modified:.how-to-release.html Log: Update to new APACHE_RELEASE format. Revision ChangesPath 1.53 +4 -4 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.52 retrieving revision 1.53 diff -u -r1.52 -r1.53 --- how-to-release.html 1998/10/10 10:58:07 1.52 +++ how-to-release.html 1999/01/10 08:15:51 1.53 @@ -137,10 +137,10 @@ from ``CODEApache/1.EMX.Y/EM-dev/CODE'' to ``CODEApache/1.EMX.Y/EM/CODE''. Then also change CODEAPACHE_RELEASE/CODE in the same file from - ``CODE1EMXXYYZZ/EM/CODE'' to ``CODE1EMXXYY/EMSTRONG99/STRONG/CODE''. + ``CODE1EMXXYYZZ/EM000/CODE'' to ``CODE1EMXXYY/EM100/CODE''. The format is something like - CODEprintf(%d%02d%02d%02d, major, minor, bugfix, - betaseq)/CODE. BR Also update the Windows registry key: + CODEprintf(%d%02d%02d%d%02d, major, minor, bugfix, final, + beta)/CODE. BR Also update the Windows registry key: edit SAMPsrc/os/win32/registry.c/SAMP and change the CODEVERSION/CODE from CODE1.EMX.Y/EM dev/CODE to the string CODE1.EMX.Y/EM/CODE. @@ -256,7 +256,7 @@ LI Change CODESERVER_VERSION/CODE in CODEsrc/include/httpd.h/CODE from ``CODEApache/1.EMX.Y/EM/CODE'' to ``CODEApache/1.EMX.(Y+1)/EM-dev/CODE'' and change - CODEAPACHE_RELEASE/CODE to CODE1EMXX(YY+1)/EM01/CODE.BR + CODEAPACHE_RELEASE/CODE to CODE1EMXX(YY+1)/EM000/CODE.BR In the CODEVERSION/CODE macro in SAMPsrc/os/win32/registry.c/SAMP, increase the version number and re-insert the ``nbsp;dev'' suffix (change the string
cvs commit: apache-devsite how-to-release.html
pcs 99/01/10 08:32:50 Modified:.how-to-release.html Log: We know build the InstallShield installer not .zip files for Windows, so don't confuse the instructions. Revision ChangesPath 1.55 +2 -61 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.54 retrieving revision 1.55 diff -u -r1.54 -r1.55 --- how-to-release.html 1999/01/10 08:21:00 1.54 +++ how-to-release.html 1999/01/10 16:32:49 1.55 @@ -363,67 +363,8 @@ BR H2How to build an Apache Windows release/H2 -FONT COLOR=redNote:/FONT These instructions are temporary, until -we have a working installation of InstallShield, which will eventually -be used to distribute Apache for Windows. At that time, these -instructions will be replaced. For building an installation with -InstallShield 2, see A HREF=how-to-release-win32how to build a -release of Apache for Windows/A. - -OL - -HR - - STRONG[ Building a source release ]/STRONGBR - P - LIFollow the instructions numbered 3-7 for Unix, to build an Apache - distribution. Be sure to use CVS running on Windows, so that the - linebreaks will be correct (alternately, export the repository with - Unix, and convert all text files - all text files - from \n to - \r\n) - P - LICreate a zipfile, using your favorite zip program, containing the - CODEapache_1.EMX.Y/EM/CODE directory. Name this zipfile - CODEapache_1.EMX.Y/EM-src.zip/CODE. - - P - HR - STRONG[ Building a binary release ]/STRONGBR - P - LIFirst, build the source release (see above). - P - LICompile and install a release version of Apache:BR - CODESTRONGgt; nmake /f Makefile.nt _apacher/STRONG/CODEBR - CODESTRONGgt; nmake /f Makefile.nt installr/STRONG/CODE - P - LIRename the directoryBR - CODESTRONGgt; move \Apache \Apache_1.EMX.Y/EM/STRONG/CODE - P - LIMove the configuration files into the correct placeBR - CODESTRONGgt; copy conf\access.conf-dist-win - \Apache_1.EMX.Y/EM\access.conf-dist/STRONG/CODEBR - CODESTRONGgt; copy conf\httpd.conf-dist-win - \Apache_1.EMX.Y/EM\httpd.conf-dist/STRONG/CODEBR - CODESTRONGgt; copy conf\srm.conf-dist-win - \Apache_1.EMX.Y/EM\srm.conf-dist/STRONG/CODEBR - CODESTRONGgt; copy conf\mime.types - \Apache_1.EMX.Y/EM\mime.types/STRONG/CODEBR - CODESTRONGgt; copy conf\magic - \Apache_1.EMX.Y/EM\magic/STRONG/CODE - P - LIMove the HTML documents into placeBR - CODESTRONGgt; copy htdocs \Apache_1.EMX.Y/EM\htdocs /s/STRONG/CODE - P - LICopy the readme fileBR - CODESTRONGgt; copy README.NT \Apache_1.EMX.Y/EM\readme.txt/STRONG/CODE - P - LIInstall the Visual C++ runtime DLLs, wherever it is they need to - go (???) - P - LICreate a zipfile of CODE\Apache_1.EMX.Y/EM/CODE named - CODEapache_1.EMX.Y/EM-bin.zip/CODE. - -/OL +See A HREF=how-to-release-win32how to build a release of Apache +for Windows/A. !--#include virtual=footer.html --
cvs commit: apache-devsite how-to-release.html
martin 98/10/10 03:58:07 Modified:.how-to-release.html Log: Update CHANGES after release Revision ChangesPath 1.52 +9 -3 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.51 retrieving revision 1.52 diff -u -r1.51 -r1.52 --- how-to-release.html 1998/10/09 09:29:52 1.51 +++ how-to-release.html 1998/10/10 10:58:07 1.52 @@ -262,17 +262,23 @@ number and re-insert the ``nbsp;dev'' suffix (change the string ``CODE1.EMX.Y/EM/CODE'' to ``CODE1.EMX.(Y+1)/EMnbsp;dev/CODE''; note the SPACE character instead of the hyphen).BR - BR Additionally make sure that the Configure script's version + Additionally make sure that the Configure script's version knowledge for the CODESHARED_CORE/CODE reflects the new version.revision.patchlevel triple. Look for the line ``CODEV=1 R=EMX/EM P=EMY/EM/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly.BR + Finally, add a new line + ``CODEChanges with Apache 1.EMX.(Y+1)/EM:/CODE'' to the + head of the SAMPsrc/CHANGES/SAMP file for the + forthcoming fixes in the new version.BR CODESTRONG$ vi src/include/httpd.h \BR nbsp;nbsp;nbsp;nbsp;nbsp;src/os/win32/registry.c \BR - nbsp;nbsp;nbsp;nbsp;nbsp;src/Configure/STRONG/CODEBR + nbsp;nbsp;nbsp;nbsp;nbsp;src/Configure \BR + nbsp;nbsp;nbsp;nbsp;nbsp;src/CHANGES/STRONG/CODEBR CODESTRONG$ cvs commit src/include/httpd.h \BR nbsp;nbsp;nbsp;nbsp;nbsp;src/os/win32/registry.c \BR - nbsp;nbsp;nbsp;nbsp;nbsp;src/Configure/STRONG/CODEBR + nbsp;nbsp;nbsp;nbsp;nbsp;src/Configure \BR + nbsp;nbsp;nbsp;nbsp;nbsp;src/CHANGES/STRONG/CODEBR CODESTRONG$ cd ../STRONG/CODEBR P HR
cvs commit: apache-devsite how-to-release.html
martin 98/10/09 02:29:52 Modified:.how-to-release.html Log: Minor changes Revision ChangesPath 1.51 +9 -7 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.50 retrieving revision 1.51 diff -u -r1.50 -r1.51 --- how-to-release.html 1998/10/07 12:23:50 1.50 +++ how-to-release.html 1998/10/09 09:29:52 1.51 @@ -147,7 +147,7 @@ BR CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR CODESTRONG$ vi src/os/win32/registry.c/STRONG/CODEBR - CODESTRONG$ cvs commit src/include/httpd.h src/os/win32/registry.c src/Configure/STRONG/CODE + CODESTRONG$ cvs commit src/include/httpd.h src/os/win32/registry.c/STRONG/CODE P LI Make sure your PGP keys are already present in the CODEKEYS/CODE file. If they are not, extract your public key using the @@ -156,7 +156,7 @@ P LI Tag the sources for this release:BR (EMnote: be sure to tag the whole thing, not just CODEsrc/CODE/EM!)BR - CODESTRONG$ cvs tag APACHE_1_X_Y/STRONG/CODE + CODESTRONG$ cvs tag APACHE_1_EMX_Y/EM/STRONG/CODE P HR STRONG[ For all releases ]/STRONGBR @@ -166,7 +166,7 @@ beside the existing CVS tree in CODEapache-1.EMX/EM/CODE)BR CODESTRONG$ cd ../STRONG/CODEBR CODESTRONG$ umask 022/STRONG/CODEBR - CODESTRONG$ cvs export -r APACHE_1_X_Y -d apache_1.EMX.Y/EM apache-1.EMX/EM/STRONG/CODEBR + CODESTRONG$ cvs export -r APACHE_1_EMX_Y/EM -d apache_1.EMX.Y/EM apache-1.EMX/EM/STRONG/CODEBR CODESTRONG$ cd apache_1.EMX.Y/EM/STRONG/CODEBR UL LIFONT COLOR=redNote:/FONT There is a known problem @@ -174,7 +174,7 @@ and later. If this affects you, you will need to do a checkout instead:BR CODESTRONG$ umask 022/STRONG/CODEBR - CODESTRONG$ cvs checkout -r APACHE_1_X_Y -d apache_1.EMX.Y/EM apache-1.EMX/EM/STRONG/CODEBR + CODESTRONG$ cvs checkout -r APACHE_1_EMX_Y/EM -d apache_1.EMX.Y/EM apache-1.EMX/EM/STRONG/CODEBR CODESTRONG$ cd apache_1.EMX.Y/EM/STRONG/CODEBR /UL P @@ -262,9 +262,8 @@ number and re-insert the ``nbsp;dev'' suffix (change the string ``CODE1.EMX.Y/EM/CODE'' to ``CODE1.EMX.(Y+1)/EMnbsp;dev/CODE''; note the SPACE character instead of the hyphen).BR - BR Additionally make sure that the - Configure script's version knowledge for the - CODESHARED_CORE/CODE reflects the new + BR Additionally make sure that the Configure script's version + knowledge for the CODESHARED_CORE/CODE reflects the new version.revision.patchlevel triple. Look for the line ``CODEV=1 R=EMX/EM P=EMY/EM/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly.BR @@ -304,6 +303,9 @@ in CODEdev.apache.org/CODE in the CODE/pub/apache/dist/CODE directory. /UL + If the Win32 binary is already built and tested at this point, + you can add it to the dist directory as well as to the + CODEbinaries/win32//CODE directory. P LI Checkout the Apache site if needed into a scratch directory:BR CODESTRONG$ cvs checkout apache-site/STRONG/CODE
cvs commit: apache-devsite how-to-release.html
martin 98/10/06 03:10:46 Modified:.how-to-release.html Log: Updates - and corrections to my earlier commit Revision ChangesPath 1.45 +30 -18apache-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.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- how-to-release.html 1998/10/05 11:12:19 1.44 +++ how-to-release.html 1998/10/06 10:10:46 1.45 @@ -60,7 +60,7 @@ CODESTRONG$ vi Announcement/STRONG/CODEBR CODESTRONG$ cvs commit Announcement/STRONG/CODEBR CODESTRONG$ cd ../STRONG/CODEBR - CODESTRONG$ rm -rf apache-1.X/STRONG/CODE + CODESTRONG$ cvs release -d apache-1.X/STRONG/CODE P HR STRONG[ Building the source release ]/STRONGBR @@ -131,22 +131,22 @@ LI Change CODESERVER_VERSION/CODE in TTsrc/include/httpd.h/TT from ``CODEApache/1.X.Y-dev/CODE'' to ``CODEApache/1.X.Y/CODE''. Then also change - CODEAPACHE_RELEASE/CODE in same file from + CODEAPACHE_RELEASE/CODE in the same file from ``CODE1XXYYZZ/CODE'' to ``CODE1XXYYSTRONG99/STRONG/CODE''. The format is something like CODEprintf(%d%02d%02d%02d, major, minor, bugfix, - betaseq)/CODE. Additionally make sure the Configure scripts version + betaseq)/CODE. Also update the Windows registry key: edit + SAMPsrc/os/win32/registry.c/SAMP and change the + CODEVERSION/CODE from 1.X.Y dev to the string 1.X.Y. + Additionally make sure the Configure scripts version knowledge for the CODESHARED_CORE/CODE reflects the correct version.revision.patchlevel triple. Look for the line ``CODEV=1 R=3 P=2/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly. BR CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR + CODESTRONG$ vi src/os/win32/registry.c/STRONG/CODEBR CODESTRONG$ vi src/Configure/STRONG/CODEBR - CODESTRONG$ 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 - SAMPos/win32/registry.c/SAMP for more details. + CODESTRONG$ cvs commit src/include/httpd.h src/os/win32/registry.c src/Configure/STRONG/CODE P LI Tag the sources for this release:BR (EMnote: be sure to tag the whole thing, not just CODEsrc/CODE/EM!)BR @@ -155,10 +155,12 @@ HR STRONG[ For all releases ]/STRONGBR P -LI Make an export version of the distribution:BR +LI Make an export version of the distribution: (this creates a second + subdirectory CODEapache-1.X.Y/CODE for the exported version + beside the existing CVS tree in CODEapache-1.X/CODE)BR CODESTRONG$ cd ../STRONG/CODEBR CODESTRONG$ umask 022/STRONG/CODEBR - CODESTRONG$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3/STRONG/CODEBR + CODESTRONG$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache-1.X/STRONG/CODEBR CODESTRONG$ cd apache_1.X.Y/STRONG/CODEBR UL LIFONT COLOR=redNote:/FONT There is a known problem @@ -166,7 +168,7 @@ and later. If this affects you, you will need to do a checkout instead:BR CODESTRONG$ umask 022/STRONG/CODEBR - CODESTRONG$ cvs checkout -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3/STRONG/CODEBR + CODESTRONG$ cvs checkout -r APACHE_1_X_Y -d apache_1.X.Y apache-1.X/STRONG/CODEBR CODESTRONG$ cd apache_1.X.Y/STRONG/CODEBR /UL P @@ -221,12 +223,16 @@ LI Remember the CHANGES file:BR CODESTRONG$ cp apache_1.X.Y/src/CHANGES ./STRONG/CODE P +LI Cleanup: (this deletes the export tree: it is now no longer + required. We still need the CVS tree, see below)BR + CODESTRONG$ rm -fr apache_1.X.Y/STRONG/CODE +P LI Make the tarball available for testing purposes: (http://dev.apache.org/)BR + CODESTRONG$ chmod 664 CHANGES apache_1.X.Y.tar.*/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.Z /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.Z.asc /pub/httpd/dist/STRONG/CODEBR - CODESTRONG$ chmod 664 apache_1.X.Y.tar.*/STRONG/CODEBR UL LIFONT COLOR=redNote:/FONT If rolling the tarball remotely, you should use CODEscp/CODE to place them @@ -238,19 +244,24 @@ STRONG[ Only for final releases, not for internal pre-releases ]/STRONGBR P LI cd back into the CVS tree location.BR - CODESTRONG$ cd apache-1.X.Y/STRONG/CODE + CODESTRONG$ cd apache-1.X/STRONG/CODE P LI Change CODESERVER_VERSION/CODE in
cvs commit: apache-devsite how-to-release.html
martin 98/10/06 07:56:22 Modified:.how-to-release.html Log: Cosmetics Revision ChangesPath 1.46 +9 -6 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.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- how-to-release.html 1998/10/06 10:10:46 1.45 +++ how-to-release.html 1998/10/06 14:56:21 1.46 @@ -135,11 +135,12 @@ ``CODE1XXYYZZ/CODE'' to ``CODE1XXYYSTRONG99/STRONG/CODE''. The format is something like CODEprintf(%d%02d%02d%02d, major, minor, bugfix, - betaseq)/CODE. Also update the Windows registry key: edit - SAMPsrc/os/win32/registry.c/SAMP and change the - CODEVERSION/CODE from 1.X.Y dev to the string 1.X.Y. - Additionally make sure the Configure scripts version - knowledge for the CODESHARED_CORE/CODE reflects the correct + betaseq)/CODE. BR Also update the Windows registry key: + edit SAMPsrc/os/win32/registry.c/SAMP and change the + CODEVERSION/CODE from CODE1.X.Y dev/CODE to the + string CODE1.X.Y/CODE.BR Additionally make sure the + Configure scripts version knowledge for the + CODESHARED_CORE/CODE reflects the correct version.revision.patchlevel triple. Look for the line ``CODEV=1 R=3 P=2/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly. BR @@ -223,7 +224,7 @@ LI Remember the CHANGES file:BR CODESTRONG$ cp apache_1.X.Y/src/CHANGES ./STRONG/CODE P -LI Cleanup: (this deletes the export tree: it is now no longer +LI Cleanup:BR(this deletes the export tree: it is now no longer required. We still need the CVS tree, see below)BR CODESTRONG$ rm -fr apache_1.X.Y/STRONG/CODE P @@ -261,6 +262,8 @@ P HR LI Cleanup:BR + (delete the CVS tree, after verification that it does not + contain any uncommitted changes)BR CODESTRONG$ cvs release -d apache-1.X/STRONG/CODE P HR
cvs commit: apache-devsite how-to-release.html
martin 98/10/06 08:05:30 Modified:.how-to-release.html Log: More cosmetics Revision ChangesPath 1.47 +3 -4 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.46 retrieving revision 1.47 diff -u -r1.46 -r1.47 --- how-to-release.html 1998/10/06 14:56:21 1.46 +++ how-to-release.html 1998/10/06 15:05:29 1.47 @@ -228,7 +228,7 @@ required. We still need the CVS tree, see below)BR CODESTRONG$ rm -fr apache_1.X.Y/STRONG/CODE P -LI Make the tarball available for testing purposes: (http://dev.apache.org/)BR +LI Make the tarball available for testing purposes: (http://dev.apache.org/dist/)BR CODESTRONG$ chmod 664 CHANGES apache_1.X.Y.tar.*/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist/STRONG/CODEBR @@ -266,9 +266,8 @@ contain any uncommitted changes)BR CODESTRONG$ cvs release -d apache-1.X/STRONG/CODE P +STRONG[ Now wait for the group to test and approve the tarball ]/STRONG HR -STRONG[ Wait for group to test and approve the tarball ]/STRONGBR -HR STRONG[ Final release steps Uafter/U the group has approved the tarball ]/STRONGBR P @@ -276,7 +275,7 @@ these instructions until the group really approves the tarball !/EM P -LI Make the distribution available: (http://www.apache.org/)BR +LI Make the distribution available: (http://www.apache.org/dist/)BR CODESTRONG$ cp CHANGES /pub/apache/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz /pub/apache/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist/STRONG/CODEBR
cvs commit: apache-devsite how-to-release.html
martin 98/10/06 13:33:43 Modified:.how-to-release.html Log: Add pointer to copies of Announcement Revision ChangesPath 1.48 +49 -18apache-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 @@ POnce a release is built (A HREF=#tarballsee below/A), it is time to announce it to the world. Ideally, the Announcement -should be composed STRONGbefore/STRONG the Release is actually built. So -we describe these steps at the beginning. +should be composed and committed STRONGbefore/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 - CODESTRONG$ cvs checkout apache-1.X/STRONG/CODEBR + CODESTRONG$ cvs checkout apache-1.X/Announcement/STRONG/CODEBR CODESTRONG$ cd apache-1.X/STRONG/CODEBR CODESTRONG$ vi Announcement/STRONG/CODEBR CODESTRONG$ cvs commit Announcement/STRONG/CODEBR CODESTRONG$ cd ../STRONG/CODEBR CODESTRONG$ cvs release -d apache-1.X/STRONG/CODE + P + STRONGNote:/STRONG This document is also present in the + CODEapache-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 ]/STRONGBR @@ -112,9 +116,10 @@ will be noted. PFONT COLOR=redImportant:/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) -EMmust/EM be bumped resulting in a new tag, tarball and release. +is rolled, there is STRONGno going back/STRONG. If there are +problems with the tarball, the version number (either the rev-level +or beta-level) EMmust/EM be bumped resulting in a new tag, +tarball and release. OL HR @@ -139,7 +144,7 @@ edit SAMPsrc/os/win32/registry.c/SAMP and change the CODEVERSION/CODE from CODE1.X.Y dev/CODE to the string CODE1.X.Y/CODE.BR Additionally make sure the - Configure scripts version knowledge for the + Configure script's version knowledge for the CODESHARED_CORE/CODE reflects the correct version.revision.patchlevel triple. Look for the line ``CODEV=1 R=3 P=2/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly. @@ -149,9 +154,14 @@ CODESTRONG$ vi src/Configure/STRONG/CODEBR CODESTRONG$ 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 CODEKEYS/CODE + file. If they are not, extract your public key using the + ``CODEpgpnbsp;-kxa/CODE'' command, add them to the + CODEKEYS/CODE file and commit it before tagging. +P LI Tag the sources for this release:BR (EMnote: be sure to tag the whole thing, not just CODEsrc/CODE/EM!)BR - CODESTRONG$ cvs tag APACHE_1_X_Y ./STRONG/CODE + CODESTRONG$ cvs tag APACHE_1_X_Y/STRONG/CODE P HR STRONG[ For all releases ]/STRONGBR @@ -228,7 +238,8 @@ required. We still need the CVS tree, see below)BR CODESTRONG$ 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 CODESTRONG$ chmod 664 CHANGES apache_1.X.Y.tar.*/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist/STRONG/CODEBR @@ -253,9 +264,9 @@ CODEAPACHE_RELEASE/CODE to CODE1XX(YY+1)01/CODE.BR In the CODEVERSION/CODE macro in SAMPsrc/os/win32/registry.c/SAMP, increase the version - number and re-insert the dev suffix (change the string - ``CODE1.X.Y/CODE'' to ``CODE1.X.(Y+1) dev/CODE''; note - the SPACE character instrad of the hyphen).BR + number and re-insert the ``nbsp;dev'' suffix (change the string + ``CODE1.X.Y/CODE'' to ``CODE1.X.(Y+1)nbsp;dev/CODE''; note + the SPACE character instead of the hyphen).BR CODESTRONG$ vi src/include/httpd.h src/os/win32/registry.c/STRONG/CODEBR CODESTRONG$ cvs commit src/include/httpd.h src/os/win32/registry.c/STRONG/CODEBR CODESTRONG$ cd
cvs commit: apache-devsite how-to-release.html
martin 98/10/06 13:36:50 Modified:.how-to-release.html Log: correct CHANGES name to apache-site/dist/CHANGES_1.X Revision ChangesPath 1.49 +1 -1 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.48 retrieving revision 1.49 diff -u -r1.48 -r1.49 --- how-to-release.html 1998/10/06 20:33:42 1.48 +++ how-to-release.html 1998/10/06 20:36:48 1.49 @@ -288,7 +288,7 @@ P LI Make the distribution available (in A HREF=http://www.apache.org/dist/;http://www.apache.org/dist//A):BR - CODESTRONG$ cp CHANGES /pub/apache/dist/STRONG/CODEBR + CODESTRONG$ cp CHANGES /pub/apache/dist/CHANGES_1.X/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz /pub/apache/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.Z /pub/apache/dist/STRONG/CODEBR
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 ChangesPath
1.44 +14 -16apache-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 CODEsrc/Configure/CODE and adjust it
accordingly.
BR
CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR
- CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODEBR
CODESTRONG$ vi src/Configure/STRONG/CODEBR
- CODESTRONG$ cvs commit src/Configure/STRONG/CODE
+ CODESTRONG$ 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 @@
CODESTRONG$ 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
CODESTRONG$ cd htdocs/manual/STRONG/CODEBR
CODESTRONG$ ./expand.pl/STRONG/CODEBR
CODESTRONG$ rm ./expand.pl/STRONG/CODEBR
@@ -221,11 +220,8 @@
P
LI Remember the CHANGES file:BR
CODESTRONG$ cp apache_1.X.Y/src/CHANGES ./STRONG/CODE
-P
-LI Cleanup:BR
- CODESTRONG$ 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
CODESTRONG$ cp apache_1.X.Y.tar.gz
/pub/httpd/dist/STRONG/CODEBR
CODESTRONG$ cp apache_1.X.Y.tar.gz.asc
/pub/httpd/dist/STRONG/CODEBR
CODESTRONG$ cp apache_1.X.Y.tar.Z
/pub/httpd/dist/STRONG/CODEBR
@@ -242,20 +238,23 @@
STRONG[ Only for final releases, not for internal pre-releases
]/STRONGBR
P
LI cd back into the CVS tree location.BR
- CODESTRONG$ cd apache-1.X/STRONG/CODE
+ CODESTRONG$ cd apache-1.X.Y/STRONG/CODE
P
LI Change CODESERVER_VERSION/CODE in CODEsrc/include/httpd.h/CODE
from ``CODEApache/1.X.Y/CODE'' to
``CODEApache/1.X.(Y+1)-dev/CODE'' and change
CODEAPACHE_RELEASE/CODE to CODE1XX(YY+1)01/CODE.BR
CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR
- CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODE
+ CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODEBR
+ CODESTRONG$ cd ../STRONG/CODEBR
P
+HR
LI Cleanup:BR
- CODESTRONG$ cd ../STRONG/CODEBR
- CODESTRONG$ rm -rf apache-1.X/STRONG/CODE
+ CODESTRONG$ rm -rf apache-1.X.Y/STRONG/CODE
P
HR
+STRONG[ Wait for group to test and approve the tarball ]/STRONGBR
+HR
STRONG[ Final release steps Uafter/U the group has approved the
tarball ]/STRONGBR
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
CODESTRONG$ cp CHANGES /pub/apache/dist/STRONG/CODEBR
CODESTRONG$ cp apache_1.X.Y.tar.gz
/pub/apache/dist/STRONG/CODEBR
CODESTRONG$ cp apache_1.X.Y.tar.gz.asc
/pub/apache/dist/STRONG/CODEBR
@@ -296,8 +295,7 @@
for the web server:BR
CODESTRONG$ umask 002/STRONG/CODEBR
CODESTRONG$ cd /pub/apache//STRONG/CODEBR
- CODESTRONG$ cvs update index.html/STRONG/CODEBR
- CODESTRONG$ cvs update dist/index.html/STRONG/CODE
+ CODESTRONG$ cvs update index.html dist/README.html/STRONG/CODE
P
LI Create an empty directory for future patches:BR
CODESTRONG$ mkdir patches/apply_to_1.X.Y/STRONG/CODE
@@ -349,14 +347,14 @@
CODESTRONGgt; copy conf\httpd.conf-dist-win
\Apache_1.X.Y\httpd.conf-dist/STRONG/CODEBR
CODESTRONGgt; copy conf\srm.conf-dist-win
- \Apache_1.X.Y\srm.conf/STRONG/CODEBR
+ \Apache_1.X.Y\srm.conf-dist/STRONG/CODEBR
CODESTRONGgt; copy conf\mime.types
\Apache_1.X.Y\mime.types/STRONG/CODEBR
CODESTRONGgt; copy conf\magic
\Apache_1.X.Y\magic/STRONG/CODE
P
LIMove the HTML documents into placeBR
- CODESTRONGgt; copy htdocs \Apache_1.X.Y\htdocs/STRONG/CODE
+ CODESTRONGgt; copy htdocs \Apache_1.X.Y\htdocs /s/STRONG/CODE
P
LICopy the readme fileBR
CODESTRONGgt; copy README.NT
\Apache_1.X.Y\readme.txt/STRONG/CODE
cvs commit: apache-devsite how-to-release.html
rse 98/09/21 12:54:45 Modified:.how-to-release.html Log: Some fixes and enhancements for the next tarball rolling time... Revision ChangesPath 1.43 +6 -1 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.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- how-to-release.html 1998/07/21 10:28:43 1.42 +++ how-to-release.html 1998/09/21 19:54:44 1.43 @@ -141,7 +141,7 @@ P=2/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly. BR CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR - CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODE + CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODEBR CODESTRONG$ vi src/Configure/STRONG/CODEBR CODESTRONG$ cvs commit src/Configure/STRONG/CODE P @@ -215,6 +215,10 @@ CODEKEYS/CODE file!BR /UL P +LI Test the tarball signatures:BR + CODESTRONG$ pgp apache_1.X.Y.tar.gz.asc apache_1.X.Y.tar.gz/STRONG/CODEBR + CODESTRONG$ pgp apache_1.X.Y.tar.Z.asc apache_1.X.Y.tar.Z/STRONG/CODEBR +P LI Remember the CHANGES file:BR CODESTRONG$ cp apache_1.X.Y/src/CHANGES ./STRONG/CODE P @@ -226,6 +230,7 @@ CODESTRONG$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.Z /pub/httpd/dist/STRONG/CODEBR CODESTRONG$ cp apache_1.X.Y.tar.Z.asc /pub/httpd/dist/STRONG/CODEBR + CODESTRONG$ chmod 664 apache_1.X.Y.tar.*/STRONG/CODEBR UL LIFONT COLOR=redNote:/FONT If rolling the tarball remotely, you should use CODEscp/CODE to place them
cvs commit: apache-devsite how-to-release.html
rse 98/07/21 03:28:45 Modified:.how-to-release.html Log: Make sure the V.R.P triple for SHARED_CORE is correct when releasing. Revision ChangesPath 1.42 +7 -1 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.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- how-to-release.html 1998/06/07 01:49:58 1.41 +++ how-to-release.html 1998/07/21 10:28:43 1.42 @@ -135,9 +135,15 @@ ``CODE1XXYYZZ/CODE'' to ``CODE1XXYYSTRONG99/STRONG/CODE''. The format is something like CODEprintf(%d%02d%02d%02d, major, minor, bugfix, - betaseq)/CODE.BR + betaseq)/CODE. Additionally make sure the Configure scripts version + knowledge for the CODESHARED_CORE/CODE reflects the correct + version.revision.patchlevel triple. Look for the line ``CODEV=1 R=3 + P=2/CODE'' inside CODEsrc/Configure/CODE and adjust it accordingly. + BR CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODE + CODESTRONG$ vi src/Configure/STRONG/CODEBR + CODESTRONG$ cvs commit 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
cvs commit: apache-devsite how-to-release.html
jim 98/06/06 18:49:59 Modified:.how-to-release.html Log: Some changes Revision ChangesPath 1.41 +11 -3 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.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- how-to-release.html 1998/06/06 14:03:50 1.40 +++ how-to-release.html 1998/06/07 01:49:58 1.41 @@ -71,7 +71,10 @@ HR STRONG[ Posting the Announcement ]/STRONGBR P - LIOnce built, CODEAnnouncement/CODE should be + LIOnce the tarball is built, give the mirrors a good 24 hours + to get up to sync. This is really important if this this + a final (i.e.: non-beta) release. + LINow, CODEAnnouncement/CODE should be posted to the following places: UL LIUnmoderated UseNet newsgroups (should be crossposted) @@ -91,6 +94,10 @@ /UL /UL P + LIMake sure that CODEAnnouncement.txt/CODE and + CODEAnnouncement.html/CODE in CODEapache-site/CODE + in the CODEdist/CODE directory are updated to include + these changes. LIBask in the glow /OL @@ -125,8 +132,9 @@ from ``CODEApache/1.X.Y-dev/CODE'' to ``CODEApache/1.X.Y/CODE''. Then also change CODEAPACHE_RELEASE/CODE in same file from - ``CODE1XXYYZZ/CODE'' to ``CODE1XXYY99/CODE''. The format is - something like CODEprintf(%d%02d%02d%02d, major, minor, bugfix, + ``CODE1XXYYZZ/CODE'' to ``CODE1XXYYSTRONG99/STRONG/CODE''. + The format is something like + CODEprintf(%d%02d%02d%02d, major, minor, bugfix, betaseq)/CODE.BR CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODE
cvs commit: apache-devsite how-to-release.html
brian 98/06/06 07:03:50 Modified:.how-to-release.html Log: Expanding the tree out isn't a good idea for a number of reasons - the mirror sites end up having to pull down a lot of files, there's no guarantee the tree will be around forever so building links to it is not a good idea, and all the files can be accessed anyways through cvsweb.cgi. Revision ChangesPath 1.40 +0 -6 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.39 retrieving revision 1.40 diff -u -r1.39 -r1.40 --- how-to-release.html 1998/05/22 00:31:14 1.39 +++ how-to-release.html 1998/06/06 14:03:50 1.40 @@ -280,12 +280,6 @@ CODESTRONG$ cvs update index.html/STRONG/CODEBR CODESTRONG$ 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 - CODESTRONG$ cd dist/STRONG/CODEBR - CODESTRONG$ gunzip lt;apache_1.X.Y.tar.gz | tar xvf -/STRONG/CODE -P LI Create an empty directory for future patches:BR CODESTRONG$ mkdir patches/apply_to_1.X.Y/STRONG/CODE /OL
cvs commit: apache-devsite how-to-release.html
jim 98/04/15 17:36:48 Modified:.how-to-release.html Log: main - include Revision ChangesPath 1.37 +6 -6 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.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- how-to-release.html 1998/04/15 17:52:34 1.36 +++ how-to-release.html 1998/04/16 00:36:47 1.37 @@ -121,15 +121,15 @@ HR STRONG[ Only for final releases, not for internal pre-releases ]/STRONGBR P -LI Change CODESERVER_VERSION/CODE in TTsrc/main/httpd.h/TT +LI Change CODESERVER_VERSION/CODE in TTsrc/include/httpd.h/TT from ``CODEApache/1.X.Y-dev/CODE'' to ``CODEApache/1.X.Y/CODE''. Then also change CODEAPACHE_RELEASE/CODE in same file from ``CODE1XXYYZZ/CODE'' to ``CODE1XXYY99/CODE''. The format is something like CODEprintf(%d%02d%02d%02d, major, minor, bugfix, betaseq)/CODE.BR - CODESTRONG$ vi src/main/httpd.h/STRONG/CODEBR - CODESTRONG$ cvs commit src/main/httpd.h/STRONG/CODE + CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR + CODESTRONG$ cvs commit src/include/httpd.h/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 @@ -228,12 +228,12 @@ LI cd back into the CVS tree location.BR CODESTRONG$ cd apache-1.X/STRONG/CODE P -LI Change CODESERVER_VERSION/CODE in CODEsrc/main/httpd.h/CODE +LI Change CODESERVER_VERSION/CODE in CODEsrc/include/httpd.h/CODE from ``CODEApache/1.X.Y/CODE'' to ``CODEApache/1.X.(Y+1)-dev/CODE'' and change CODEAPACHE_RELEASE/CODE to CODE1XX(YY+1)01/CODE.BR - CODESTRONG$ vi src/main/httpd.h/STRONG/CODEBR - CODESTRONG$ cvs commit src/main/httpd.h/STRONG/CODE + CODESTRONG$ vi src/include/httpd.h/STRONG/CODEBR + CODESTRONG$ cvs commit src/include/httpd.h/STRONG/CODE P LI Cleanup:BR CODESTRONG$ cd ../STRONG/CODEBR
cvs commit: apache-devsite how-to-release.html
rse 98/04/15 00:05:01
Modified:.how-to-release.html
Log:
Don't distribute .indent.pro files: they are out-of-date and there is no need
for the user to indent some of the distributed code theirself.
Revision ChangesPath
1.34 +3 -2 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.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- how-to-release.html 1998/04/14 18:54:33 1.33
+++ how-to-release.html 1998/04/15 07:05:00 1.34
@@ -161,10 +161,11 @@
CODESTRONG$ cp src/Configuration.tmpl
src/Configuration/STRONG/CODE
P
LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE,
CODEHTTP_Features.tsv/CODE,
- CODEsrc/INDENT/CODE, various CODE.cvsignore/CODE files
- and the developer's test subdirectories:BR
+ CODEsrc/INDENT/CODE, various CODE.cvsignore/CODE and
+ CODE.indent.pro/CODE files and the developer's test
subdirectories:BR
CODESTRONG$ rm STATUS RULES.CVS HTTP_Features.tsv
src/INDENT/STRONG/CODEBR
CODESTRONG$ find . -name .cvsignore -exec rm {}
\;/STRONG/CODEBR
+ CODESTRONG$ find . -name .indent.pro -exec rm {}
\;/STRONG/CODEBR
CODESTRONG$ rm -rf src/test/STRONG/CODEBR
CODESTRONG$ rm -rf src/modules/test/STRONG/CODE
UL
cvs commit: apache-devsite how-to-release.html
rse 98/04/15 02:31:27
Modified:.how-to-release.html
Log:
Remove another dotfile which need not be distributed: src/.gdbinit
Revision ChangesPath
1.35 +1 -1 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.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- how-to-release.html 1998/04/15 07:05:00 1.34
+++ how-to-release.html 1998/04/15 09:31:26 1.35
@@ -163,7 +163,7 @@
LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE,
CODEHTTP_Features.tsv/CODE,
CODEsrc/INDENT/CODE, various CODE.cvsignore/CODE and
CODE.indent.pro/CODE files and the developer's test
subdirectories:BR
- CODESTRONG$ rm STATUS RULES.CVS HTTP_Features.tsv
src/INDENT/STRONG/CODEBR
+ CODESTRONG$ rm STATUS RULES.CVS HTTP_Features.tsv src/INDENT
src/.gdbinit/STRONG/CODEBR
CODESTRONG$ find . -name .cvsignore -exec rm {}
\;/STRONG/CODEBR
CODESTRONG$ find . -name .indent.pro -exec rm {}
\;/STRONG/CODEBR
CODESTRONG$ rm -rf src/test/STRONG/CODEBR
cvs commit: apache-devsite how-to-release.html
rse 98/04/14 11:54:33
Modified:.how-to-release.html
Log:
Make sure HTTP_Features.tsv is removed and the
checked-out documents have correct permissions.
Revision ChangesPath
1.33 +3 -2 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.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- how-to-release.html 1998/04/14 14:38:40 1.32
+++ how-to-release.html 1998/04/14 18:54:33 1.33
@@ -160,10 +160,10 @@
LI Create CODEsrc/Configuration/CODE file:BR
CODESTRONG$ cp src/Configuration.tmpl
src/Configuration/STRONG/CODE
P
-LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE,
+LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE,
CODEHTTP_Features.tsv/CODE,
CODEsrc/INDENT/CODE, various CODE.cvsignore/CODE files
and the developer's test subdirectories:BR
- CODESTRONG$ rm STATUS RULES.CVS src/INDENT/STRONG/CODEBR
+ CODESTRONG$ rm STATUS RULES.CVS HTTP_Features.tsv
src/INDENT/STRONG/CODEBR
CODESTRONG$ find . -name .cvsignore -exec rm {}
\;/STRONG/CODEBR
CODESTRONG$ rm -rf src/test/STRONG/CODEBR
CODESTRONG$ rm -rf src/modules/test/STRONG/CODE
@@ -278,6 +278,7 @@
P
LI Update the checked-out versions of the CODEapache-site/CODE
documents
for the web server:BR
+ CODESTRONG$ umask 002/STRONG/CODEBR
CODESTRONG$ cd /pub/apache//STRONG/CODEBR
CODESTRONG$ cvs update index.html/STRONG/CODEBR
CODESTRONG$ cvs update dist/index.html/STRONG/CODE
cvs commit: apache-devsite how-to-release.html
rse 98/03/05 07:33:58
Modified:.how-to-release.html
Log:
The stuff in src/modules/test/ is of the same type as
the stuff in src/test, so better to leave it out in the
distribution tarball...
Revision ChangesPath
1.30 +3 -2 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.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- how-to-release.html 1998/03/05 11:58:34 1.29
+++ how-to-release.html 1998/03/05 15:33:57 1.30
@@ -160,10 +160,11 @@
P
LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE,
CODEsrc/INDENT/CODE, various CODE.cvsignore/CODE files
- and the developer's test subdirectory:BR
+ and the developer's test subdirectories:BR
CODESTRONG$ rm STATUS RULES.CVS src/INDENT/STRONG/CODEBR
- CODESTRONG$ find . -name .cvsignore -exec rm {} \;/STRONG/CODE
+ CODESTRONG$ find . -name .cvsignore -exec rm {}
\;/STRONG/CODEBR
CODESTRONG$ rm -rf src/test/STRONG/CODEBR
+ CODESTRONG$ rm -rf src/modules/test/STRONG/CODE
UL
LIFONT COLOR=redNote:/FONT If you needed to do a
CODEcheckout/CODE instead of a CODEexport/CODE, you
cvs commit: apache-devsite how-to-release.html how-to-release-win32.html apache.iwz
pcs 98/02/24 07:04:27 Modified:.how-to-release.html how-to-release-win32.html Removed: .apache.iwz Log: Remove the apache.iwz IS2 file (now in the source tree). Update the how-to-release documents a bit for this, and with some information about licence key version information. Revision ChangesPath 1.28 +10 -5 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.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- how-to-release.html 1998/02/23 08:33:31 1.27 +++ how-to-release.html 1998/02/24 15:04:24 1.28 @@ -128,6 +128,10 @@ betaseq)/CODE.BR CODESTRONG$ vi src/main/httpd.h/STRONG/CODEBR CODESTRONG$ cvs commit src/main/httpd.h/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 + SAMPos/win32/registry.c/SAMP for more details. P LI Tag the sources for this release:BR (EMnote: be sure to tag the whole thing, not just CODEsrc/CODE/EM!)BR @@ -265,11 +269,12 @@ BR H2How to build an Apache Windows release/H2 -FONT COLOR=redNote:/FONT These instructions are temporary, until we have a -working installation of InstallShield, which will eventually be used to -distribute Apache for Windows. At that time, these instructions will be -replaced. For building an installation with InstallShield 2, see -A HREF=how-to-release-win32How to Release Apache for Windows/A. +FONT COLOR=redNote:/FONT These instructions are temporary, until +we have a working installation of InstallShield, which will eventually +be used to distribute Apache for Windows. At that time, these +instructions will be replaced. For building an installation with +InstallShield 2, see A HREF=how-to-release-win32how to build a +release of Apache for Windows/A. OL 1.2 +57 -14apache-devsite/how-to-release-win32.html Index: how-to-release-win32.html === RCS file: /export/home/cvs/apache-devsite/how-to-release-win32.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- how-to-release-win32.html 1998/02/22 18:30:14 1.1 +++ how-to-release-win32.html 1998/02/24 15:04:25 1.2 @@ -25,8 +25,8 @@ BLOCKQUOTE BLOCKQUOTE This document describes how to release Apache for Windows (95 and -NT). It is an appendix to the main -A HREF=how-to-releaseHow to Release Apache/A document. +NT). It is an appendix to the main A HREF=how-to-releasehow to +build a release of Apache/A document. /BLOCKQUOTE /BLOCKQUOTE /BLOCKQUOTE @@ -41,7 +41,7 @@ LICreate an install directory to hold the files used when building the installer LIConfigure the InstallShield configuration file - LIBuild the installer DLL + LIBuild the installer DLL and copy it to the install directory LIBuild Apache and install it to the install directory LIUse InstallShield to build the files from the install directory into the single .EXE installer @@ -94,23 +94,66 @@ LIBConfigure the InstallShield Configuration File/BP Apache for Windows is packaged using InstallShield 2. This requires an -InstallShield configuration file SAMPA -HREF=apache.iwzapache.iwz/A/SAMP. Unfortunately InstallShield's -configuration file contains hard-coded absolute paths to the -individual files. If your install directory (step 1) is -SAMPC:\Apache/SAMP then you do not need to update the apache.iwz -file. If you use another directory, search and replace -SAMPC:\Apache/SAMP with your directory in SAMPapache.iwz/SAMP. +InstallShield configuration file +SAMPos/win32/installer/apache.iwz/SAMP. Unfortunately +InstallShield's configuration file contains hard-coded absolute paths +to the individual files. If your install directory (step 1) is +SAMPC:\Apache/SAMP then you do not need to update the +SAMPapache.iwz/SAMP file. If you use another directory, search and +replace SAMPC:\Apache/SAMP with your directory in +SAMPapache.iwz/SAMP. + +P + +BNote/B: This is probably a good time to check that the version +information in the SAMPapache.iwz/SAMP file is up-to-date. The +version is stored in these locations: + +P + +UL + + LISet the Visual Design, Application Information, Version. This + should contain the full version number, eg. 1.3 or 1.3b5. + + LISet the Visual Design, Main Window, Main Title. As above. + + LIMake Registry Changes, Registry Keys. The key + HKLM\SOFTWARE\Apache Group\Apache should contain a subkey + containing the version number which does not change across beta + release. For example,
cvs commit: apache-devsite how-to-release.html
rse 98/02/23 00:33:31
Modified:.how-to-release.html
Log:
missing blank
Revision ChangesPath
1.27 +1 -1 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.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- how-to-release.html 1998/02/22 18:30:15 1.26
+++ how-to-release.html 1998/02/23 08:33:31 1.27
@@ -155,7 +155,7 @@
CODESTRONG$ cp src/Configuration.tmpl
src/Configuration/STRONG/CODE
P
LI Remove CODESTATUS/CODE, CODERULES.CVS/CODE and
- CODEsrc/INDENT/CODEfile and various CODE.cvsignore/CODE
files:BR
+ CODEsrc/INDENT/CODE file and various CODE.cvsignore/CODE
files:BR
CODESTRONG$ rm STATUS RULES.CVS src/INDENT/STRONG/CODEBR
CODESTRONG$ find . -name .cvsignore -exec rm {} \;/STRONG/CODE
UL
cvs commit: apache-devsite how-to-release.html
rse 98/02/09 01:27:30
Modified:.how-to-release.html
Log:
- a few cosmetics: made the windows part equal to the unix
part, added a document article-style header, added
paragraph tags to make the look consistent again
- added command to remove src/INDENT because we already
remove STATUS and src/INDENT is of the same type so
both should be removed
Revision ChangesPath
1.23 +70 -25apache-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.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- how-to-release.html 1998/02/08 15:23:36 1.22
+++ how-to-release.html 1998/02/09 09:27:29 1.23
@@ -14,12 +14,35 @@
!--#include virtual=header.html --
P
+BR
-h1Announcing a New Release/h1
+div align=center
+H1How to build a release of Apache/H1
+Alexei Kosut lt;[EMAIL PROTECTED]gt;br
+Ralf S. Engelschall lt;[EMAIL PROTECTED]gt;br
+Jim Jagielski lt;[EMAIL PROTECTED]gt;
+/div
+
+blockquote
+blockquote
+blockquote
+This document describes the typical release cycle the release manager has to
+step through when creating a new Apache release. It is written down as a
+step-by-step instruction list and should be followed exactly as specified to
+avoid problems or inconsistencies both in the created tarballs and the source
+repository.
+/blockquote
+/blockquote
+/blockquote
+
+p
+br
+h2Announcing a New Release/h2
pOnce a release is built (A HREF=#tarballsee below/A),
it is time to announce it to the world. Ideally, the Announcement
-should be composed before the Release is actually built.
+should be composed strongbefore/strong the Release is actually built. So
+we describe these steps at the beginning.
ol
hr
@@ -31,15 +54,21 @@
to reflect the current state of affairs concerning the
release. For example, the Release Version should reflect
what is actually being announced. Also, the key enhancements
- of the Release should be noted.
- licodecommit/code the changes.
-
+ of the Release should be noted.br
+ codeb$ cvs checkout apache-1.3/b/codebr
+ codeb$ cd apache-1.3/b/codebr
+ codeb$ vi Announcement/b/codebr
+ codeb$ cvs commit Announcement/b/code
+ p
hr
-
- b[ Posting the Announcement ]/bbr
+ b[ Building the source release ]/bbr
p
liFirst, build the source release (A HREF=#tarballsee below/A)
if not already done.
+ p
+ hr
+ b[ Posting the Announcement ]/bbr
+ p
liOnce built, codeAnnouncement/code should be
posted to the following places:
ul
@@ -59,14 +88,15 @@
licode[EMAIL PROTECTED]/code
/ul
/ul
+ p
liBask in the glow
/ol
P
+BR
-hr
+h2A NAME=tarballHow to build an Apache Unix release/A/h2
-H1A NAME=tarballHow to build a release of Apache/A/H1
PFONT COLOR=redNote:/FONT The below assumes that you are
using codessh/code to login to your codedev.apache.org/code
account. If you are rolling the tarball remotely, the differences
@@ -80,6 +110,8 @@
LI cd into the codeapache-1.3/code CVS tree.br
codeb$ cd apache-1.3/b/code
P
+
+hr
b[ Only for final releases, not for internal pre-releases ]/bbr
P
LI Change codeSERVER_VERSION/code in ttsrc/main/httpd.h/tt
@@ -99,7 +131,6 @@
HR
b[ For all releases ]/bbr
P
-P
LI Make an export version of the distribution:br
codeb$ cd ../b/codebr
codeb$ umask 022/b/codebr
@@ -118,8 +149,9 @@
LI Create codesrc/Configuration/code file:br
codeb$ cp src/Configuration.tmpl src/Configuration/b/code
P
-LI Remove codeSTATUS/code and codeRULES.CVS/code file and various
code.cvsignore/code files:br
- codeb$ rm STATUS RULES.CVS/b/codebr
+LI Remove codeSTATUS/code, codeRULES.CVS/code and
+ codesrc/INDENT/codefile and various code.cvsignore/code
files:br
+ codeb$ rm STATUS RULES.CVS src/INDENT/b/codebr
codeb$ find . -name .cvsignore -exec rm {} \;/b/code
UL
LIFONT COLOR=redNote:/FONT If you needed to do a
@@ -154,9 +186,12 @@
codeb$ rm -rf apache_1.X.Y/b/code
P
LI Sign the distribution files:br
- (emnote: be sure your PGP key is already in the codeKEYS/code
file/em!)br
codeb$ pgp -sba apache_1.X.Y.tar.gz/b/codebr
codeb$ pgp -sba apache_1.X.Y.tar.Z/b/codebr
+ UL
+ LIFONT COLOR=redNote:/FONT Be sure your PGP key is already in
the
+ codeKEYS/code file/em!)br
+ /UL
P
LI Make the tarball available for testing purposes:br
codeb$ cp apache_1.X.Y.tar.gz /pub/httpd/dist/b/codebr
@@ -169,9 +204,15 @@
in codedev.apache.org/code in the code/pub/httpd/dist/code
cvs commit: apache-devsite how-to-release.html
jim 98/02/09 05:30:11 Modified:.how-to-release.html Log: Formalize the 'tarball is bad' rules Revision ChangesPath 1.24 +5 -0 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.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- how-to-release.html 1998/02/09 09:27:29 1.23 +++ how-to-release.html 1998/02/09 13:30:10 1.24 @@ -102,6 +102,11 @@ account. If you are rolling the tarball remotely, the differences will be noted. +PFONT COLOR=redImportant:/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) +EMmust/EM be bumped resulting in a new tag, tarball and release. + OL HR LI Checkout the Apache source if needed into a scratch directory:br
cvs commit: apache-devsite how-to-release.html
jim 98/02/08 07:23:37 Modified:.how-to-release.html Log: info about pre-release tarball Revision ChangesPath 1.22 +15 -0 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.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- how-to-release.html 1998/01/27 07:52:00 1.21 +++ how-to-release.html 1998/02/08 15:23:36 1.22 @@ -158,6 +158,21 @@ codeb$ pgp -sba apache_1.X.Y.tar.gz/b/codebr codeb$ pgp -sba apache_1.X.Y.tar.Z/b/codebr P +LI Make the tarball available for testing purposes:br + codeb$ cp apache_1.X.Y.tar.gz /pub/httpd/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.Z /pub/httpd/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.Z.asc /pub/httpd/dist/b/codebr + UL + LIFONT COLOR=redNote:/FONT If rolling the tarball + remotely, you should use codescp/code to place them + in codedev.apache.org/code in the code/pub/httpd/dist/code + directory. + /UL + P + emFONT COLOR=redNote:/FONT Do not continue with the rest of + these instructions until the group approves the tarball !/em +P LI Make the distribution available:br codeb$ cp apache_1.X.Y.tar.gz /pub/apache/dist/b/codebr codeb$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist/b/codebr
cvs commit: apache-devsite how-to-release.html
dgaudet 97/12/20 12:35:10
Modified:.how-to-release.html
Log:
remove STATUS on release
Revision ChangesPath
1.20 +2 -2 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.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- how-to-release.html 1997/10/20 21:09:20 1.19
+++ how-to-release.html 1997/12/20 20:35:09 1.20
@@ -118,8 +118,8 @@
LI Create codesrc/Configuration/code file:br
codeb$ cp src/Configuration.tmpl src/Configuration/b/code
P
-LI Remove codeRULES.CVS/code file and various code.cvsignore/code
files:br
- codeb$ rm RULES.CVS/b/codebr
+LI Remove codeSTATUS/code and codeRULES.CVS/code file and various
code.cvsignore/code files:br
+ codeb$ rm STATUS RULES.CVS/b/codebr
codeb$ find . -name .cvsignore -exec rm {} \;/b/code
UL
LIFONT COLOR=redNote:/FONT If you needed to do a
cvs commit: apache-devsite how-to-release.html index.html
jim 97/10/20 14:09:21
Modified:.how-to-release.html index.html
Log:
Document various changes:
o apache - apachen
o some remote considerations if rolling the tarball
o some HTML cleanup
Revision ChangesPath
1.19 +78 -40apache-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.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- how-to-release.html 1997/10/18 15:53:38 1.18
+++ how-to-release.html 1997/10/20 21:09:20 1.19
@@ -3,6 +3,7 @@
HEAD
TITLEHow to build a release of Apache/TITLE
/HEAD
+!-- Yeah, we know; there are some HTML lint-errors in this --
!-- Background white, links blue (unvisited), navy (visited), red (active)
--
BODY
BGCOLOR=#FF
@@ -16,9 +17,9 @@
h1Announcing a New Release/h1
-pOnce a release is built, it is time to announce it to the
-world. Ideally, the Announcement should be composed before the
-Release is actually built.
+pOnce a release is built (A HREF=#tarballsee below/A),
+it is time to announce it to the world. Ideally, the Announcement
+should be composed before the Release is actually built.
ol
hr
@@ -37,7 +38,8 @@
b[ Posting the Announcement ]/bbr
p
- liFirst, build the source release (see below) if not already done.
+ liFirst, build the source release (A HREF=#tarballsee below/A)
+ if not already done.
liOnce built, codeAnnouncement/code should be
posted to the following places:
ul
@@ -64,24 +66,31 @@
hr
-H1How to build a release of Apache/H1
-
-PFirst, use ssh to login to your dev.apache.org account and cd to a scratch
-directory.
+H1A NAME=tarballHow to build a release of Apache/A/H1
+PFONT COLOR=redNote:/FONT The below assumes that you are
+using codessh/code to login to your codedev.apache.org/code
+account. If you are rolling the tarball remotely, the differences
+will be noted.
OL
HR
+LI Checkout the Apache source if needed into a scratch directory:br
+ codeb$ cvs checkout apachen/b/code
+P
+LI cd into the codeapachen/code CVS tree.br
+ codeb$ cd apachen/b/code
+P
b[ Only for final releases, not for internal pre-releases ]/bbr
P
-LI Change codeSERVER_VERSION/code in ttsrc/httpd.h/tt
+LI Change codeSERVER_VERSION/code in ttsrc/main/httpd.h/tt
from ``codeApache/1.X.Y-dev/code'' to
``codeApache/1.X.Y/code''. Then also change
codeAPACHE_RELEASE/code in same file from
``code1XXYYZZ/code'' to ``code1XXYY99/code''. The format is
something like codeprintf(%d%02d%02d%02d, major, minor, bugfix,
betaseq)/code.br
- codeb$ vi src/httpd.h/b/codebr
- codeb$ cvs commit src/httpd.h/b/code
+ codeb$ vi src/main/httpd.h/b/codebr
+ codeb$ cvs commit src/main/httpd.h/b/code
P
LI Tag the sources for this release:br
(inote: be sure to tag the whole thing, not just
codesrc/code/i!)br
@@ -92,9 +101,19 @@
P
P
LI Make an export version of the distribution:br
+ codeb$ cd ../b/codebr
codeb$ umask 022/b/codebr
- codeb$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y
apache/b/codebr
- codeb$ cd apache_1.X.Y/b/code
+ codeb$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y
apachen/b/codebr
+ codeb$ cd apache_1.X.Y/b/codebr
+ UL
+ LIFONT COLOR=redNote:/FONT There is a known problem
+ using codecvs export/code remotely with codecvs-1.9/code
+ and later. If this affects you, you will need to do a checkout
+ instead:br
+ codeb$ umask 022/b/codebr
+ codeb$ cvs checkout -r APACHE_1_X_Y -d apache_1.X.Y
apachen/b/codebr
+ codeb$ cd apache_1.X.Y/b/codebr
+ /UL
P
LI Create codesrc/Configuration/code file:br
codeb$ cp src/Configuration.tmpl src/Configuration/b/code
@@ -102,6 +121,12 @@
LI Remove codeRULES.CVS/code file and various code.cvsignore/code
files:br
codeb$ rm RULES.CVS/b/codebr
codeb$ find . -name .cvsignore -exec rm {} \;/b/code
+ UL
+ LIFONT COLOR=redNote:/FONT If you needed to do a
+ codecheckout/code instead of a codeexport/code, you
+ will also need to remove the CVS administrative files:br
+ codeb$ find . -type d -name CVS -exec rm -rf {} \;/b/code
+ /UL
P
LI Add an empty codelogs//code directory:br
codeb$ mkdir logs/b/code
@@ -138,27 +163,40 @@
codeb$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist/b/codebr
codeb$ cp apache_1.X.Y.tar.Z /pub/apache/dist/b/codebr
codeb$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist/b/codebr
-P
-LI Adjust the README.html file as required:br
- liEdit codeREADME.html/code from codeapache-site/code CVS
tree
- (it's in
cvs commit: apache-devsite how-to-release.html
jim 97/10/18 08:53:38 Modified:.how-to-release.html Log: README.html now available via cvs Revision ChangesPath 1.18 +3 -1 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.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- how-to-release.html 1997/10/17 22:45:43 1.17 +++ how-to-release.html 1997/10/18 15:53:38 1.18 @@ -140,7 +140,9 @@ codeb$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist/b/codebr P LI Adjust the README.html file as required:br - codeb$ vi /pub/apache/dist/README.html/b/codebr + liEdit codeREADME.html/code from codeapache-site/code CVS tree + (it's in the code./dist/code subdirectory) + licodecommit/code the changes P LI Adjust the Apache index.html file as required:br ol
cvs commit: apache-devsite how-to-release.html
jim 97/10/17 13:11:12 Modified:.how-to-release.html Log: Add some notes on how and where to announce releases Revision ChangesPath 1.15 +48 -2 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.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- how-to-release.html 1997/09/10 22:41:53 1.14 +++ how-to-release.html 1997/10/17 20:11:12 1.15 @@ -12,6 +12,52 @@ ALINK=#FF !--#include virtual=header.html -- +P + +h1Announcing a New Release/h1 + +pOnce a release is built, it is time to announce it to the +world. Ideally, the Announcement should be composed before the +Release is actually built. + +ol +hr + + b[ Adjusting Announcement to taste ]/bbr + p + liA prototype codeAnnouncement/code is included in + the main CVS source tree. This file should be updated + to reflect the current state of affairs concerning the + release. For example, the Release Version should reflect + what is actually being announced. Also, the key enhancements + of the Release should be noted. + licodecommit/code the changes. + + hr + + b[ Posting the Announcement ]/bbr + p + liFirst, build the source release (see below) if not already done. + liOnce built, codeAnnouncement/code should be + posted to the following places: + ul +liUseNet newsgroups + ul + licodecomp.infosystems.www.servers.unix/code + licodecomp.infosystems.www.servers.ms-windows/code + licodecomp.infosystems.www.servers.misc/code + /ul +liMailing Lists + ul + licode[EMAIL PROTECTED]/code + /ul + /ul + liBask in the glow +/ol + +P + +hr H1How to build a release of Apache/H1 @@ -128,7 +174,7 @@ liFirst, build the source release (see above). liCompile and install a release version of Apache:Mbr codeb nmake /f Makefile.nt _apacher/b/codebr - codeb namke /f Makefile.nt installr/b/code + codeb nmake /f Makefile.nt installr/b/code liRename the directorybr codeb move \Apache \Apache_1.X.Y/b/code liMove the configuration files into the correct placebr @@ -155,6 +201,6 @@ !--#include virtual=footer.html -- -Written by Alexei Kosut and Ralf S. Engelschall. +Written by Alexei Kosut and Ralf S. Engelschall and Others /BODY /HTML
cvs commit: apache-devsite how-to-release.html
jim 97/10/17 13:59:36 Modified:.how-to-release.html Log: More groups to announce to Revision ChangesPath 1.16 +2 -0 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.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- how-to-release.html 1997/10/17 20:11:12 1.15 +++ how-to-release.html 1997/10/17 20:59:35 1.16 @@ -43,9 +43,11 @@ ul liUseNet newsgroups ul + licodecomp.infosystems.www.announce/code licodecomp.infosystems.www.servers.unix/code licodecomp.infosystems.www.servers.ms-windows/code licodecomp.infosystems.www.servers.misc/code + licodede.comm.infosystems.www.servers/code /ul liMailing Lists ul
cvs commit: apache-devsite how-to-release.html
jim 97/10/17 15:45:43 Modified:.how-to-release.html Log: More detail: edit index.html, README.html Revision ChangesPath 1.17 +20 -2 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.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- how-to-release.html 1997/10/17 20:59:35 1.16 +++ how-to-release.html 1997/10/17 22:45:43 1.17 @@ -41,14 +41,17 @@ liOnce built, codeAnnouncement/code should be posted to the following places: ul -liUseNet newsgroups +liUnmoderated UseNet newsgroups (should be crossposted) ul - licodecomp.infosystems.www.announce/code licodecomp.infosystems.www.servers.unix/code licodecomp.infosystems.www.servers.ms-windows/code licodecomp.infosystems.www.servers.misc/code licodede.comm.infosystems.www.servers/code /ul +liModerated UseNet newsgroups (do bnot/b crosspost) + ul + licodecomp.infosystems.www.announce/code + /ul liMailing Lists ul licode[EMAIL PROTECTED]/code @@ -129,6 +132,21 @@ (emnote: be sure your PGP key is already in the codeKEYS/code file/em!)br codeb$ pgp -sba apache_1.X.Y.tar.gz/b/codebr codeb$ pgp -sba apache_1.X.Y.tar.Z/b/codebr +P +LI Make the distribution available:br + codeb$ cp apache_1.X.Y.tar.gz /pub/apache/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.Z /pub/apache/dist/b/codebr + codeb$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist/b/codebr +P +LI Adjust the README.html file as required:br + codeb$ vi /pub/apache/dist/README.html/b/codebr +P +LI Adjust the Apache index.html file as required:br + ol + liEdit codeindex.html/code from codeapache-site/code CVS tree + licodecommit/code the changes + /ol P HR b[ Only for final releases, not for internal pre-releases ]/bbr
cvs commit: apache-devsite how-to-release.html
akosut 97/09/10 15:41:55 Modified:.how-to-release.html Log: Add some tenative instructions for creating pre-InstallSheild Windows releases. Revision ChangesPath 1.14 +59 -0 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.13 retrieving revision 1.14 diff -u -u -r1.13 -r1.14 --- how-to-release.html 1997/08/22 07:22:34 1.13 +++ how-to-release.html 1997/09/10 22:41:53 1.14 @@ -94,6 +94,65 @@ /OL P + +hr + +h2How to build an Apache Windows release/h2 + +blockquote +strongNote:/strong These instructions are temporary, until we have a +working installation of InstallShield, which will eventually be used to +distribute Apache for Windows. At that time, these instructions will be +replaced./strong +/blockquote + +ol + +hr + + b[ Building a source release ]/bbr + p + liFollow the instructions numbered 3-7 for Unix, to build an Apache + distribution. Be sure to use CVS running on Windows, so that the + linebreaks will be correct (alternately, export the repository with + Unix, and convert all text files - all text files - from \n to + \r\n) + liCreate a zipfile, using your favorite zip program, containing the + codeapache_1.X.Y/code directory. Name this zipfile + codeapache_1.X.Y-src.zip/code. + + hr + + b[ Building a binary release ]/bbr + p + liFirst, build the source release (see above). + liCompile and install a release version of Apache:Mbr + codeb nmake /f Makefile.nt _apacher/b/codebr + codeb namke /f Makefile.nt installr/b/code + liRename the directorybr + codeb move \Apache \Apache_1.X.Y/b/code + liMove the configuration files into the correct placebr + codeb copy conf\access.conf-dist-win + \Apache_1.X.Y\access.conf-dist/b/codebr + codeb copy conf\httpd.conf-dist-win + \Apache_1.X.Y\httpd.conf-dist/b/codebr + codeb copy conf\srm.conf-dist-win + \Apache_1.X.Y\srm.conf/b/codebr + codeb copy conf\mime.types + \Apache_1.X.Y\mime.types/b/codebr + codeb copy conf\magic + \Apache_1.X.Y\magic/b/code + liMove the HTML documents into placebr + codeb copy htdocs \Apache_1.X.Y\htdocs/b/code + liCopy the readme filebr + codeb copy README.NT \Apache_1.X.Y\readme.txt/b/code + liInstall the Visual C++ runtime DLLs, wherever it is they need to + go (???) + liCreate a zipfile of code\Apache_1.X.Y/code named + codeapache_1.X.Y-bin.zip/code. + +/ol + !--#include virtual=footer.html -- Written by Alexei Kosut and Ralf S. Engelschall.
cvs commit: apache-devsite how-to-release.html
rse 97/08/22 00:22:35 Modified:.how-to-release.html Log: Both generic and specific version numbers confuse. Revision ChangesPath 1.13 +1 -1 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.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- how-to-release.html 1997/08/21 01:14:18 1.12 +++ how-to-release.html 1997/08/22 07:22:34 1.13 @@ -62,7 +62,7 @@ codeb$ cd ../../../b/code P LI Roll the distribution tarball:br - codeb$ tar cvf apache_1.X.Y.tar apache_1.2.3/b/codebr + codeb$ tar cvf apache_1.X.Y.tar apache_1.X.Y/b/codebr P LI Make the final packed distribution files:br codeb$ cp -p apache_1.X.Y.tar xapache_1.X.Y.tar/b/codebr
cvs commit: apache-devsite how-to-release.html
fielding97/08/20 18:14:19 Modified:.how-to-release.html Log: And your little dog Toto, too. (test .tar.Z file using zcat) Revision ChangesPath 1.12 +2 -1 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.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- how-to-release.html 1997/08/21 01:09:41 1.11 +++ how-to-release.html 1997/08/21 01:14:18 1.12 @@ -70,8 +70,9 @@ codeb$ mv xapache_1.X.Y.tar apache_1.X.Y.tar/b/codebr codeb$ compress apache_1.X.Y.tar/b/codebr P -LI Verify gzip'd tar file (check for errors):br +LI Test the packed tar files and check for errors:br codeb$ gunzip -c apache_1.X.Y.tar.gz | tar tvf -/b/codebr + codeb$ zcat apache_1.X.Y.tar.Z | tar tvf -/b/codebr P LI Cleanup:br codeb$ rm -rf apache_1.X.Y/b/code
cvs commit: apache-devsite how-to-release.html
rse 97/08/18 23:52:17 Modified:.how-to-release.html Log: Accept empty dirs in the tarball. This is needed because we create special tarballs: the empty logs directory have to exists there. Revision ChangesPath 1.10 +6 -4 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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- how-to-release.html 1997/08/12 09:06:37 1.9 +++ how-to-release.html 1997/08/19 06:52:16 1.10 @@ -63,13 +63,15 @@ codeb$ cd htdocs/manual/b/codebr codeb$ ./expand.pl/b/codebr codeb$ rm ./expand.pl/b/codebr - codeb$ cd ../../b/code + codeb$ cd ../../../b/code P -LI Roll the tarball (with sorted files!):br - codeb$ cd ../b/codebr +LI Roll the distribution tarball. Here you have two possible options:br + Variant (a), professional tarball with sorted files (irecommended!/i):br codeb$ tar cvf apache_1.X.Y.tar \/b/codebr codebnbsp;nbsp;`find apache_1.X.Y -depth -print | sort |\/b/codebr - codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code + codebnbsp;nbsp;nbsp;perl -nle 'print $_ if (-f $_ or (-d _ and not join(, glob $_/*)));'`/b/codebr + Variant (b), poor man's tarball with files sorted as found on filesystem:br + codeb$ tar cvf apache_1.X.Y.tar apache_1.2.3/b/codebr P LI Make the final packed distribution files:br (emnote: no codegzip -9/code here because some Tars then don't like the gunzip'ed result/em)br
cvs commit: apache-devsite how-to-release.html
rse 97/08/07 01:57:15 Modified:. how-to-release.html Log: Fixup. Revision ChangesPath 1.8 +11 -7 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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- how-to-release.html 1997/08/06 20:19:03 1.7 +++ how-to-release.html 1997/08/07 08:57:14 1.8 @@ -49,7 +49,7 @@ codeb$ cd apache_1.X.Y/b/code P LI Create codesrc/Configuration/code file:br - codeb$ cp src/Configuration.tmpl src/Configuration/b/code + codeb$ cp -p src/Configuration.tmpl src/Configuration/b/code P LI Remove codeRULES.CVS/code file and various code.cvsignore/code files:br codeb$ rm RULES.CVS/b/codebr @@ -66,19 +66,23 @@ P LI Roll the tarball (with sorted files!):br codeb$ cd ../b/codebr - codeb$ tar cvf apache_1.2.2.tar \/b/codebr - codebnbsp;nbsp;`find apache_1.2.2 -depth -print | sort |\/b/codebr + codeb$ tar cvf apache_1.X.Y.tar \/b/codebr + codebnbsp;nbsp;`find apache_1.X.Y -depth -print | sort |\/b/codebr codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code P LI Make the final packed distribution files:br (emnote: no codegzip -9/code here because some Tars then don't like the gunzip'ed result/em)br - codeb$ gzip lt;apache_1.2.2.tar gt;apache_1.2.2.tar.gz/b/codebr - codeb$ compress lt;apache_1.2.2.tar gt;apache_1.2.2.tar.Z/b/codebr + codeb$ gzip lt;apache_1.X.Y.tar gt;apache_1.X.Y.tar.gz/b/codebr + codeb$ compress lt;apache_1.X.Y.tar gt;apache_1.X.Y.tar.Z/b/codebr +P +LI Cleanup:br + codeb$ rm -rf apache_1.X.Y/b/codebr + codeb$ rm -f apache_1.X.Y.tar/b/codebr P LI Sign the distribution files:br (emnote: be sure your PGP key is already in the codeKEYS/code file/em!)br - codeb$ pgp -sba apache_1.2.2.tar.gz/b/codebr - codeb$ pgp -sba apache_1.2.2.tar.Z/b/codebr + codeb$ pgp -sba apache_1.X.Y.tar.gz/b/codebr + codeb$ pgp -sba apache_1.X.Y.tar.Z/b/codebr P HR b[ Only for final releases, not for internal pre-releases ]/bbr
cvs commit: apache-devsite how-to-release.html
rse 97/08/06 00:19:47 Modified:. how-to-release.html Log: Overhauled the step-by-step instruction for releasing Apache. Revision ChangesPath 1.2 +85 -15apache-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.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- how-to-release.html 1997/06/17 10:43:29 1.1 +++ how-to-release.html 1997/08/06 07:19:46 1.2 @@ -1,20 +1,90 @@ +!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN +HTML + HEAD + TITLEHow to build a release of Apache/TITLE + /HEAD +!-- Background white, links blue (unvisited), navy (visited), red (active) -- + BODY + BGCOLOR=#FF + TEXT=#00 + LINK=#FF + VLINK=#80 + ALINK=#FF + +!--#include virtual=header.html -- + +BLOCKQUOTE H1How to build a release of Apache/H1 -addressOriginally from Alexei Kosut/address +Written by Ralf S. Engelschall a href=mailto:[EMAIL PROTECTED]lt;[EMAIL PROTECTED]gt/a,br +based on original work by Alexei Kosut a href=mailto:[EMAIL PROTECTED]lt;[EMAIL PROTECTED]gt/a,br + +P +OL +HR +b[ Only for final releases, not for internal pre-releases ]/bbr +P +LI Change codeSERVER_VERSION/code in ttsrc/httpd.h/ttbr + from ``codeApache/1.X.Y-dev/code'' to ``codeApache/1.X.Y/code'' and commit.br + codeb$ vi src/httpd.h/b/codebr + codeb$ cvs ci src/httpd.h/b/code +P +LI Tag the sources for this release:br + (inote: be sure to tag the whole thing, not just codesrc/code/i!)br + codeb$ cvs tag APACHE_1_X_Y ./b/code +P +HR +b[ For all releases ]/bbr +P +P +LI Make an export version of the distribution:br + codeb$ cd /tmp/b/codebr + codeb$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache/b/codebr + codeb$ cd apache_1.X.Y/b/code +P +LI Create codesrc/Configuration/code file:br + codeb$ cp src/Configuration.tmpl src/Configuration/b/code +P +LI Remove codeRULES.CVS/code file and various code.cvsignore/code files:br + codeb$ rm RULES.CVS/b/codebr + codeb$ find . -name .cvsignore -print | xargs rm/b/code +P +LI Add an empty codelogs//code directory:br + codeb$ mkdir logs/b/code +P +LI Expand the Service-Side-Include directives in the manual:br + codeb$ cd htdocs/manual/b/codebr + codeb$ ./expand.pl/b/codebr + codeb$ rm ./expand.pl/b/codebr + codeb$ cd ../../b/code +P +LI Roll the tarball (with sorted files!):br + codeb$ cd ../b/codebr + codeb$ tar cvf apache_1.2.2.tar \/b/codebr + codebnbsp;nbsp;`find apache_1.2.2 -depth -print | sort |\/b/codebr + codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code +P +LI Make the final packed distribution files:br + codeb$ gzip -9 apache_1.2.2.tar/b/codebr + codeb$ compress apache_1.2.2.tar/b/codebr +P +LI Sign the distribution files:br + (inote: be sure your PGP key is already in the codeKEYS/code file/i!)br + codeb$ pgp -sba apache_1.2.2.tar.gz/b/codebr + codeb$ pgp -sba apache_1.2.2.tar.Z/b/codebr +P +HR +b[ Only for final releases, not for internal pre-releases ]/bbr P +LI Change codeSERVER_VERSION/code in codesrc/httpd.h/code:br + from ``codeApache/1.X.Y/code'' to + ``codeApache/1.X.(Y+1)-dev/code'' and commit.br + codeb$ vi src/httpd.h/b/codebr + codeb$ cvs ci src/httpd.h/b/code +/OL +/BLOCKQUOTE -UL -LI change SERVER_VERSION in httpd.h (and commit) -LI tag it: e.g. codecvs tag APACHE_1_1b3/code - (note: be sure to tag the whole thing, not just src) -LI make an export version of the distribution, e.g.:br - codecvs export -r APACHE_1_1b3 -d apache_1.1b3 apache/code -LI Copy Configuration.tmpl to Configuration -LI Remove RULES.CVS file and various .cvsignore files (in src/ and - support/) -LI Add an empty logs directory -LI cd to the htdocs/manual directory. Run expand.pl, then delete it. -LI Tar, compress/gzip and release. -LI change SERVER_VERSION to next-version-dev (and commit) -/UL +!--#include virtual=footer.html -- + /BODY +/HTML
cvs commit: apache-devsite how-to-release.html
rse 97/08/06 00:35:54 Modified:. how-to-release.html Log: Added info about major minor bugfix betaseq in APACHE_RELEASE define. Is this the way as it is intended? Revision ChangesPath 1.3 +11 -5 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.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- how-to-release.html 1997/08/06 07:19:46 1.2 +++ how-to-release.html 1997/08/06 07:35:53 1.3 @@ -25,8 +25,13 @@ HR b[ Only for final releases, not for internal pre-releases ]/bbr P -LI Change codeSERVER_VERSION/code in ttsrc/httpd.h/ttbr - from ``codeApache/1.X.Y-dev/code'' to ``codeApache/1.X.Y/code'' and commit.br +LI First change codeSERVER_VERSION/code in ttsrc/httpd.h/tt + from ``codeApache/1.X.Y-dev/code'' to + ``codeApache/1.X.Y/code''. Then also change + codeAPACHE_RELEASE/code in same file from + ``code1XXYYZZ/code'' to ``code1XXYY99/code''. The format is + something like codeprintf(%d%02d%02d%02d, major, minor, bugfix, + betaseq)/code.br codeb$ vi src/httpd.h/b/codebr codeb$ cvs ci src/httpd.h/b/code P @@ -77,9 +82,10 @@ HR b[ Only for final releases, not for internal pre-releases ]/bbr P -LI Change codeSERVER_VERSION/code in codesrc/httpd.h/code:br - from ``codeApache/1.X.Y/code'' to - ``codeApache/1.X.(Y+1)-dev/code'' and commit.br +LI Change codeSERVER_VERSION/code in codesrc/httpd.h/code + from ``codeApache/1.X.Y/code'' to + ``codeApache/1.X.(Y+1)-dev/code'' and change + codeAPACHE_RELEASE/code to code1XX(YY+1)01/code.br codeb$ vi src/httpd.h/b/codebr codeb$ cvs ci src/httpd.h/b/code /OL
cvs commit: apache-devsite how-to-release.html
rse 97/08/06 00:40:11 Modified:. how-to-release.html Log: Ops, after gzip the .tar is gone ;-) Revision ChangesPath 1.4 +2 -2 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.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- how-to-release.html 1997/08/06 07:35:53 1.3 +++ how-to-release.html 1997/08/06 07:40:10 1.4 @@ -71,8 +71,8 @@ codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code P LI Make the final packed distribution files:br - codeb$ gzip -9 apache_1.2.2.tar/b/codebr - codeb$ compress apache_1.2.2.tar/b/codebr + codeb$ gzip -9 apache_1.2.2.tar apache_1.2.2.tar.gz/b/codebr + codeb$ compress apache_1.2.2.tar apache_1.2.2.tar.Z/b/codebr P LI Sign the distribution files:br (inote: be sure your PGP key is already in the codeKEYS/code file/i!)br
cvs commit: apache-devsite how-to-release.html
rse 97/08/06 13:13:19 Modified:. how-to-release.html Log: Added some suggestions by Marc. Revision ChangesPath 1.6 +5 -4 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.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- how-to-release.html 1997/08/06 07:46:40 1.5 +++ how-to-release.html 1997/08/06 20:13:18 1.6 @@ -33,7 +33,7 @@ something like codeprintf(%d%02d%02d%02d, major, minor, bugfix, betaseq)/code.br codeb$ vi src/httpd.h/b/codebr - codeb$ cvs ci src/httpd.h/b/code + codeb$ cvs commit src/httpd.h/b/code P LI Tag the sources for this release:br (inote: be sure to tag the whole thing, not just codesrc/code/i!)br @@ -44,7 +44,7 @@ P P LI Make an export version of the distribution:br - codeb$ cd /tmp/b/codebr + codeb$ umask 022/b/codebr codeb$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache/b/codebr codeb$ cd apache_1.X.Y/b/code P @@ -71,7 +71,8 @@ codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code P LI Make the final packed distribution files:br - codeb$ gzip -9 lt;apache_1.2.2.tar gt;apache_1.2.2.tar.gz/b/codebr + codeb$ gzip lt;apache_1.2.2.tar gt;apache_1.2.2.tar.gz/b/codebr + (note: no code-9/code here because some Tars then don't like the gunzip'ed result)br codeb$ compress lt;apache_1.2.2.tar gt;apache_1.2.2.tar.Z/b/codebr P LI Sign the distribution files:br @@ -87,7 +88,7 @@ ``codeApache/1.X.(Y+1)-dev/code'' and change codeAPACHE_RELEASE/code to code1XX(YY+1)01/code.br codeb$ vi src/httpd.h/b/codebr - codeb$ cvs ci src/httpd.h/b/code + codeb$ cvs commit src/httpd.h/b/code /OL /BLOCKQUOTE
cvs commit: apache-devsite how-to-release.html
rse 97/08/06 13:19:03 Modified:. how-to-release.html Log: Just some layout adjustments. Revision ChangesPath 1.7 +2 -2 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.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- how-to-release.html 1997/08/06 20:13:18 1.6 +++ how-to-release.html 1997/08/06 20:19:03 1.7 @@ -71,12 +71,12 @@ codebnbsp;nbsp;nbsp;perl -nle 'print $_ if -f $_;'`/b/code P LI Make the final packed distribution files:br + (emnote: no codegzip -9/code here because some Tars then don't like the gunzip'ed result/em)br codeb$ gzip lt;apache_1.2.2.tar gt;apache_1.2.2.tar.gz/b/codebr - (note: no code-9/code here because some Tars then don't like the gunzip'ed result)br codeb$ compress lt;apache_1.2.2.tar gt;apache_1.2.2.tar.Z/b/codebr P LI Sign the distribution files:br - (inote: be sure your PGP key is already in the codeKEYS/code file/i!)br + (emnote: be sure your PGP key is already in the codeKEYS/code file/em!)br codeb$ pgp -sba apache_1.2.2.tar.gz/b/codebr codeb$ pgp -sba apache_1.2.2.tar.Z/b/codebr P
