4 >Releasing a new version</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy Developer Manual"
10 HREF="index.html"><LINK
12 TITLE="Testing Guidelines"
13 HREF="testing.html"><LINK
15 TITLE="Contacting the developers, Bug Reporting and Feature Requests"
16 HREF="contact.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy Developer Manual</TH
73 >8. Releasing a new version</A
76 > To minimize trouble with distribution contents, webpage
77 errors and the like, we strongly encourage you
78 to follow this section if you prepare a new release of
79 code or new pages on the webserver.
82 > The following programs are required to follow this process:
93 > (GNU's version of make), autoconf, cvs, ???.
101 >8.1. Before the Release</A
106 >must be done by one of the
108 > prior to each new release:
116 > Make sure that everybody who has worked on the code in the last
117 couple of days has had a chance to yell <SPAN
121 they have pending changes/fixes in their pipelines.
126 > Increment the version number in <TT
130 CVS. Also, the RPM release number in
134 >. Do NOT touch version information
135 after export from CVS. <I
139 version and release data from <TT
143 Local files should not be changed, except prior to a CVS commit!!!
144 This way we are all on the same page!
149 > If the default actionsfile has changed since last release,
150 bump up its version info in this line:
161 CLASS="PROGRAMLISTING"
162 > {+add-header{X-Actions-File-Version: A.B} -filter -no-popups}
171 Then change the version info in doc/webserver/actions/index.php,
172 line: '$required_actions_file_version = "A.B";'
177 > Tag all files in CVS with the version number with
184 > (where X = major, Y
185 = minor, Z = point). Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work)
191 > The first package uploaded should be the official
195 > release. This is built with the
200 >make tarball-dist</B
203 target, and then can be uploaded with
208 >make tarball-upload</B
222 NAME="NEWRELEASE-WEB"
223 >8.2. Update the webserver</A
226 > All files must be group-readable and group-writable (or no one else
227 will be able to change them). To update the webserver, create any
228 pages locally in the <TT
232 create new directories under <TT
245 CLASS="PROGRAMLISTING"
270 >doc/webserver/user-manual</TT
274 >doc/webserver/developer-manual</TT
278 >doc/webserver/faq</TT
282 >doc/webserver/man-page</TT
286 > Please do NOT use any other means of transferring files to the
294 uploads, but will make sure that the appropriate permissions are
295 preserved for shared group access.
303 NAME="NEWRELEASE-RPM"
304 >8.3. SuSE or Red Hat</A
307 > Ensure that you have the latest code version. Hence run:
317 CLASS="PROGRAMLISTING"
319 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
320 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
338 CLASS="PROGRAMLISTING"
339 > autoheader && autoconf && ./configure
357 CLASS="PROGRAMLISTING"
358 > make suse-dist or make redhat-dist
366 > To upload the package to Sourceforge, simply issue
376 CLASS="PROGRAMLISTING"
377 > make suse-upload or make redhat-upload
385 > Go to the displayed URL and release the file publicly on Sourceforge.
393 NAME="NEWRELEASE-OS2"
397 > Ensure that you have the latest code version. Hence run:
407 CLASS="PROGRAMLISTING"
409 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
410 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
412 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
420 > You will need a mix of development tools.
421 The main compilation takes place with IBM Visual Age C++.
422 Some ancillary work takes place with GNU tools, available from
423 various sources like hobbes.nmsu.edu.
424 Specificially, you will need <TT
435 The packaging takes place with WarpIN, available from various sources, including
437 HREF="http://www.xworkplace.org/"
443 > Change directory to the <TT
447 Edit the os2build.cmd file to set the final executable filename.
456 CLASS="PROGRAMLISTING"
457 > installExeName='privoxyos2_setup_X.Y.Z.exe'
466 > file so the release number matches
478 CLASS="PROGRAMLISTING"
479 > PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
485 You're now ready to build. Run:
493 CLASS="PROGRAMLISTING"
503 > directory you will have the
504 WarpIN-installable executable.
505 Upload this anonymously to
508 >uploads.sourceforge.net/incoming</TT
510 for it, and you're done.
518 NAME="NEWRELEASE-SOLARIS"
522 > Login to Sourceforge's compilefarm via ssh
532 CLASS="PROGRAMLISTING"
533 > ssh cf.sourceforge.net
541 > Choose the right operating system (not the Debian one). If you have
555 CLASS="PROGRAMLISTING"
557 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
558 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
567 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
570 Privoxy via CVS first</A
581 CLASS="PROGRAMLISTING"
582 > autoheader && autoconf && ./configure
600 CLASS="PROGRAMLISTING"
609 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
613 > on the Sourceforge machine (no ncftpput). You now have
614 to manually upload the archive to Sourceforge's ftp server and release
623 NAME="NEWRELEASE-WINDOWS"
627 > Ensure that you have the latest code version. Hence run
637 CLASS="PROGRAMLISTING"
639 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
640 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
658 CLASS="PROGRAMLISTING"
659 > autoheader && autoconf && ./configure
675 NAME="NEWRELEASE-DEBIAN"
679 > Ensure that you have the latest code version. Hence run:
689 CLASS="PROGRAMLISTING"
691 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
692 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
710 CLASS="PROGRAMLISTING"
711 > autoheader && autoconf && ./configure
727 NAME="NEWRELEASE-MACOSX"
731 > Ensure that you have the latest code version. Hence run:
741 CLASS="PROGRAMLISTING"
743 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
744 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
746 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
754 > From the osxsetup directory, run:
762 CLASS="PROGRAMLISTING"
785 Finally, it will copy over the necessary files to the ./osxsetup/files directory
786 for further processing by <TT
792 > Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
793 name to match the release, and hit the "Create package" button.
794 If you specify ./Privoxy.pkg as the output package name, you can then create
795 the distributable zip file with the command:
803 CLASS="PROGRAMLISTING"
804 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
810 You can then upload <TT
812 >privoxyosx_setup_x.y.z.zip</TT
816 >uploads.sourceforge.net/incoming</TT
818 create a release for it, and you're done.
826 NAME="NEWRELEASE-FREEBSD"
830 > Change the version number of <SPAN
834 configure.in file. Run:
842 CLASS="PROGRAMLISTING"
843 > autoheader && autoconf && ./configure
852 > Login to Sourceforge's compilefarm via ssh:
862 CLASS="PROGRAMLISTING"
863 > ssh cf.sourceforge.net
871 > Choose the right operating system. If you have downloaded Privoxy
882 CLASS="PROGRAMLISTING"
884 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
885 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
894 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
897 Privoxy via CVS first</A
908 CLASS="PROGRAMLISTING"
909 > autoheader && autoconf && ./configure
927 CLASS="PROGRAMLISTING"
936 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
940 > on the Sourceforge machine (no ncftpput). You now have
941 to manually upload the archive to Sourceforge's ftp server and release
950 NAME="NEWRELEASE-TARBALL"
954 > Ensure that you have the latest code version. Hence run:
964 CLASS="PROGRAMLISTING"
966 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
967 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
985 CLASS="PROGRAMLISTING"
987 autoheader && autoconf && ./configure
1005 CLASS="PROGRAMLISTING"
1014 > To upload the package to Sourceforge, simply issue
1024 CLASS="PROGRAMLISTING"
1025 > make tarball-upload
1033 > Goto the displayed URL and release the file publicly on Sourceforge.
1041 NAME="NEWRELEASE-HPUX"
1045 > Ensure that you have the latest code version. Hence run:
1055 CLASS="PROGRAMLISTING"
1057 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1058 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1076 CLASS="PROGRAMLISTING"
1077 > autoheader && autoconf && ./configure
1093 NAME="NEWRELEASE-AMIGA"
1097 > Ensure that you have the latest code version. Hence run:
1107 CLASS="PROGRAMLISTING"
1109 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1110 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1128 CLASS="PROGRAMLISTING"
1129 > autoheader && autoconf && ./configure
1145 NAME="NEWRELEASE-AIX"
1149 > Login to Sourceforge's compilefarm via ssh:
1159 CLASS="PROGRAMLISTING"
1160 > ssh cf.sourceforge.net
1168 > Choose the right operating system. If you have downloaded Privoxy
1179 CLASS="PROGRAMLISTING"
1181 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1182 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1191 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1194 Privoxy via CVS first</A
1205 CLASS="PROGRAMLISTING"
1206 > autoheader && autoconf && ./configure
1224 CLASS="PROGRAMLISTING"
1233 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
1237 > on the Sourceforge machine (no ncftpput). You now have
1238 to manually upload the archive to Sourceforge's ftp server and release
1283 >Testing Guidelines</TD
1293 >Contacting the developers, Bug Reporting and Feature Requests</TD