4 >Releasing a new version</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy Developer Manual"
11 HREF="index.html"><LINK
13 TITLE="Testing Guidelines"
14 HREF="testing.html"><LINK
16 TITLE="Contacting the developers, Bug Reporting and Feature Requests"
17 HREF="contact.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy Developer Manual</TH
74 >8. Releasing a new version</A
77 > To minimize trouble with distribution contents, webpage
78 errors and the like, we strongly encourage you
79 to follow this section if you prepare a new release of
80 code or new pages on the webserver.
83 > The following programs are required to follow this process:
94 > (GNU's version of make), autoconf, cvs, ???.
102 >8.1. Before the Release</A
107 >must be done by one of the
109 > prior to each new release:
117 > Make sure that everybody who has worked on the code in the last
118 couple of days has had a chance to yell <SPAN
122 they have pending changes/fixes in their pipelines.
127 > Increment the version number in <TT
131 CVS. Also, the RPM release number in
135 >. Do NOT touch version information
136 after export from CVS. <I
140 version and release data from <TT
144 Local files should not be changed, except prior to a CVS commit!!!
145 This way we are all on the same page!
150 > If the default actionsfile has changed since last release,
151 bump up its version info in this line:
162 CLASS="PROGRAMLISTING"
163 > {+add-header{X-Actions-File-Version: A.B} -filter -no-popups}
172 Then change the version info in doc/webserver/actions/index.php,
173 line: '$required_actions_file_version = "A.B";'
178 > Tag all files in CVS with the version number with
185 > (where X = major, Y
186 = minor, Z = point). Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work)
192 > The first package uploaded should be the official
196 > release. This is built with the
201 >make tarball-dist</B
204 target, and then can be uploaded with
209 >make tarball-upload</B
223 NAME="NEWRELEASE-WEB"
224 >8.2. Update the webserver</A
227 > All files must be group-readable and group-writable (or no one else
228 will be able to change them). To update the webserver, create any
229 pages locally in the <TT
233 create new directories under <TT
246 CLASS="PROGRAMLISTING"
271 >doc/webserver/user-manual</TT
275 >doc/webserver/developer-manual</TT
279 >doc/webserver/faq</TT
283 >doc/webserver/man-page</TT
287 > Please do NOT use any other means of transferring files to the
295 uploads, but will make sure that the appropriate permissions are
296 preserved for shared group access.
304 NAME="NEWRELEASE-RPM"
305 >8.3. SuSE or Red Hat</A
308 > Ensure that you have the latest code version. Hence run:
318 CLASS="PROGRAMLISTING"
320 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
321 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
339 CLASS="PROGRAMLISTING"
340 > autoheader && autoconf && ./configure
358 CLASS="PROGRAMLISTING"
359 > make suse-dist or make redhat-dist
367 > To upload the package to Sourceforge, simply issue
377 CLASS="PROGRAMLISTING"
378 > make suse-upload or make redhat-upload
386 > Go to the displayed URL and release the file publicly on Sourceforge.
394 NAME="NEWRELEASE-OS2"
398 > Ensure that you have the latest code version. Hence run:
408 CLASS="PROGRAMLISTING"
410 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
411 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
413 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
421 > You will need a mix of development tools.
422 The main compilation takes place with IBM Visual Age C++.
423 Some ancillary work takes place with GNU tools, available from
424 various sources like hobbes.nmsu.edu.
425 Specificially, you will need <TT
436 The packaging takes place with WarpIN, available from various sources, including
438 HREF="http://www.xworkplace.org/"
444 > Change directory to the <TT
448 Edit the os2build.cmd file to set the final executable filename.
457 CLASS="PROGRAMLISTING"
458 > installExeName='privoxyos2_setup_X.Y.Z.exe'
467 > file so the release number matches
479 CLASS="PROGRAMLISTING"
480 > PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
486 You're now ready to build. Run:
494 CLASS="PROGRAMLISTING"
504 > directory you will have the
505 WarpIN-installable executable.
506 Upload this anonymously to
509 >uploads.sourceforge.net/incoming</TT
511 for it, and you're done.
519 NAME="NEWRELEASE-SOLARIS"
523 > Login to Sourceforge's compilefarm via ssh
533 CLASS="PROGRAMLISTING"
534 > ssh cf.sourceforge.net
542 > Choose the right operating system (not the Debian one). If you have
556 CLASS="PROGRAMLISTING"
558 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
559 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
568 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
571 Privoxy via CVS first</A
582 CLASS="PROGRAMLISTING"
583 > autoheader && autoconf && ./configure
601 CLASS="PROGRAMLISTING"
610 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
614 > on the Sourceforge machine (no ncftpput). You now have
615 to manually upload the archive to Sourceforge's ftp server and release
624 NAME="NEWRELEASE-WINDOWS"
628 > Ensure that you have the latest code version. Hence run
638 CLASS="PROGRAMLISTING"
640 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
641 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
659 CLASS="PROGRAMLISTING"
660 > autoheader && autoconf && ./configure
676 NAME="NEWRELEASE-DEBIAN"
680 > Ensure that you have the latest code version. Hence run:
690 CLASS="PROGRAMLISTING"
692 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
693 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
711 CLASS="PROGRAMLISTING"
712 > autoheader && autoconf && ./configure
728 NAME="NEWRELEASE-MACOSX"
732 > Ensure that you have the latest code version. Hence run:
742 CLASS="PROGRAMLISTING"
744 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
745 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
747 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
755 > From the osxsetup directory, run:
763 CLASS="PROGRAMLISTING"
786 Finally, it will copy over the necessary files to the ./osxsetup/files directory
787 for further processing by <TT
793 > Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
794 name to match the release, and hit the "Create package" button.
795 If you specify ./Privoxy.pkg as the output package name, you can then create
796 the distributable zip file with the command:
804 CLASS="PROGRAMLISTING"
805 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
811 You can then upload <TT
813 >privoxyosx_setup_x.y.z.zip</TT
817 >uploads.sourceforge.net/incoming</TT
819 create a release for it, and you're done.
827 NAME="NEWRELEASE-FREEBSD"
831 > Change the version number of <SPAN
835 configure.in file. Run:
843 CLASS="PROGRAMLISTING"
844 > autoheader && autoconf && ./configure
853 > Login to Sourceforge's compilefarm via ssh:
863 CLASS="PROGRAMLISTING"
864 > ssh cf.sourceforge.net
872 > Choose the right operating system. If you have downloaded Privoxy
883 CLASS="PROGRAMLISTING"
885 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
886 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
895 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
898 Privoxy via CVS first</A
909 CLASS="PROGRAMLISTING"
910 > autoheader && autoconf && ./configure
928 CLASS="PROGRAMLISTING"
937 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
941 > on the Sourceforge machine (no ncftpput). You now have
942 to manually upload the archive to Sourceforge's ftp server and release
951 NAME="NEWRELEASE-TARBALL"
955 > Ensure that you have the latest code version. Hence run:
965 CLASS="PROGRAMLISTING"
967 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
968 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
986 CLASS="PROGRAMLISTING"
988 autoheader && autoconf && ./configure
1006 CLASS="PROGRAMLISTING"
1015 > To upload the package to Sourceforge, simply issue
1025 CLASS="PROGRAMLISTING"
1026 > make tarball-upload
1034 > Goto the displayed URL and release the file publicly on Sourceforge.
1042 NAME="NEWRELEASE-HPUX"
1046 > Ensure that you have the latest code version. Hence run:
1056 CLASS="PROGRAMLISTING"
1058 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1059 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1077 CLASS="PROGRAMLISTING"
1078 > autoheader && autoconf && ./configure
1094 NAME="NEWRELEASE-AMIGA"
1098 > Ensure that you have the latest code version. Hence run:
1108 CLASS="PROGRAMLISTING"
1110 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1111 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1129 CLASS="PROGRAMLISTING"
1130 > autoheader && autoconf && ./configure
1146 NAME="NEWRELEASE-AIX"
1150 > Login to Sourceforge's compilefarm via ssh:
1160 CLASS="PROGRAMLISTING"
1161 > ssh cf.sourceforge.net
1169 > Choose the right operating system. If you have downloaded Privoxy
1180 CLASS="PROGRAMLISTING"
1182 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1183 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1192 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1195 Privoxy via CVS first</A
1206 CLASS="PROGRAMLISTING"
1207 > autoheader && autoconf && ./configure
1225 CLASS="PROGRAMLISTING"
1234 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
1238 > on the Sourceforge machine (no ncftpput). You now have
1239 to manually upload the archive to Sourceforge's ftp server and release
1284 >Testing Guidelines</TD
1294 >Contacting the developers, Bug Reporting and Feature Requests</TD