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, ???.
96 > Replace X, Y and Z with the actual version number (X = major, Y = minor, Z = point):
104 >8.1. Before the Release</A
109 >must be done by one of the
111 > prior to each new release.
119 > Make sure that everybody who has worked on the code in the last
120 couple of days has had a chance to yell <SPAN
124 they have pending changes/fixes in their pipelines.
129 > Increment the version number in <TT
133 CVS. Also, inrease or reset the RPM release number in
137 > as appropriate. Do <I
141 touch version information after export from CVS.
145 > will use the version and release data
150 Local files should not be changed, except prior to a CVS commit!!!
151 This way we are all on the same page!
156 > If the default actionsfile has changed since last release,
157 bump up its version info in this line:
168 CLASS="PROGRAMLISTING"
169 > {+add-header{X-Actions-File-Version: A.B} -filter -no-popups}
178 Then change the version info in doc/webserver/actions/index.php,
179 line: '$required_actions_file_version = "A.B";'
184 > Tag all files in CVS with the version number with
192 Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.
197 > The first package uploaded should be the official
201 > release. This is built with the
206 >make tarball-dist</B
209 target, and then can be uploaded with
214 >make tarball-upload</B
228 NAME="NEWRELEASE-WEB"
229 >8.2. Update the webserver</A
232 > All files must be group-readable and group-writable (or no one else
233 will be able to change them). To update the webserver, create any
234 pages locally in the <TT
238 create new directories under <TT
251 CLASS="PROGRAMLISTING"
276 >doc/webserver/user-manual</TT
280 >doc/webserver/developer-manual</TT
284 >doc/webserver/faq</TT
288 >doc/webserver/man-page</TT
292 > Please do NOT use any other means of transferring files to the
300 uploads, but will make sure that the appropriate permissions are
301 preserved for shared group access.
309 NAME="NEWRELEASE-RPM"
310 >8.3. SuSE or Red Hat</A
313 > Ensure that you have the latest code version. Hence run:
323 CLASS="PROGRAMLISTING"
324 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
325 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
344 CLASS="PROGRAMLISTING"
345 > autoheader && autoconf && ./configure
363 CLASS="PROGRAMLISTING"
364 > make suse-dist or make redhat-dist
372 > To upload the package to Sourceforge, simply issue
382 CLASS="PROGRAMLISTING"
383 > make suse-upload or make redhat-upload
391 > Go to the displayed URL and release the file publicly on Sourceforge.
399 NAME="NEWRELEASE-OS2"
403 > Ensure that you have the latest code version. Hence run:
413 CLASS="PROGRAMLISTING"
414 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
415 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
417 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
425 > You will need a mix of development tools.
426 The main compilation takes place with IBM Visual Age C++.
427 Some ancillary work takes place with GNU tools, available from
428 various sources like hobbes.nmsu.edu.
429 Specificially, you will need <TT
440 The packaging takes place with WarpIN, available from various sources, including
442 HREF="http://www.xworkplace.org/"
448 > Change directory to the <TT
452 Edit the os2build.cmd file to set the final executable filename.
461 CLASS="PROGRAMLISTING"
462 > installExeName='privoxyos2_setup_X.Y.Z.exe'
471 > file so the release number matches
483 CLASS="PROGRAMLISTING"
484 > PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
490 You're now ready to build. Run:
498 CLASS="PROGRAMLISTING"
508 > directory you will have the
509 WarpIN-installable executable.
510 Upload this anonymously to
513 >uploads.sourceforge.net/incoming</TT
515 for it, and you're done.
523 NAME="NEWRELEASE-SOLARIS"
527 > Login to Sourceforge's compilefarm via ssh
537 CLASS="PROGRAMLISTING"
538 > ssh cf.sourceforge.net
546 > Choose the right operating system (not the Debian one). If you have
560 CLASS="PROGRAMLISTING"
561 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
562 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
572 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
575 Privoxy via CVS first</A
586 CLASS="PROGRAMLISTING"
587 > autoheader && autoconf && ./configure
605 CLASS="PROGRAMLISTING"
614 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
618 > on the Sourceforge machine (no ncftpput). You now have
619 to manually upload the archive to Sourceforge's ftp server and release
628 NAME="NEWRELEASE-WINDOWS"
632 > Ensure that you have the latest code version. Hence run
642 CLASS="PROGRAMLISTING"
643 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
644 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
663 CLASS="PROGRAMLISTING"
664 > autoheader && autoconf && ./configure
680 NAME="NEWRELEASE-DEBIAN"
684 > Ensure that you have the latest code version. Hence run:
694 CLASS="PROGRAMLISTING"
695 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
696 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
715 CLASS="PROGRAMLISTING"
716 > autoheader && autoconf && ./configure
732 NAME="NEWRELEASE-MACOSX"
736 > Ensure that you have the latest code version. Hence run:
746 CLASS="PROGRAMLISTING"
747 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
748 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
750 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
758 > From the osxsetup directory, run:
766 CLASS="PROGRAMLISTING"
789 Finally, it will copy over the necessary files to the ./osxsetup/files directory
790 for further processing by <TT
796 > Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
797 name to match the release, and hit the "Create package" button.
798 If you specify ./Privoxy.pkg as the output package name, you can then create
799 the distributable zip file with the command:
807 CLASS="PROGRAMLISTING"
808 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
814 You can then upload <TT
816 >privoxyosx_setup_x.y.z.zip</TT
820 >uploads.sourceforge.net/incoming</TT
822 create a release for it, and you're done.
830 NAME="NEWRELEASE-FREEBSD"
834 > Change the version number of <SPAN
838 configure.in file. Run:
846 CLASS="PROGRAMLISTING"
847 > autoheader && autoconf && ./configure
856 > Login to Sourceforge's compilefarm via ssh:
866 CLASS="PROGRAMLISTING"
867 > ssh cf.sourceforge.net
875 > Choose the right operating system.
885 CLASS="PROGRAMLISTING"
886 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
887 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
906 CLASS="PROGRAMLISTING"
907 > autoheader && autoconf && ./configure
925 CLASS="PROGRAMLISTING"
934 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
938 > on the Sourceforge machine (no ncftpput). You now have
939 to manually upload the archive to Sourceforge's ftp server and release
948 NAME="NEWRELEASE-TARBALL"
952 > Ensure that you have the right code version. Hence run:
962 CLASS="PROGRAMLISTING"
963 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
964 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
983 CLASS="PROGRAMLISTING"
984 > autoheader && autoconf && ./configure
1002 CLASS="PROGRAMLISTING"
1011 > To upload the package to Sourceforge, simply issue
1021 CLASS="PROGRAMLISTING"
1022 > make tarball-upload
1030 > Goto the displayed URL and release the file publicly on Sourceforge.
1038 NAME="NEWRELEASE-HPUX"
1042 > Ensure that you have the latest code version. Hence run:
1052 CLASS="PROGRAMLISTING"
1053 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1054 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1073 CLASS="PROGRAMLISTING"
1074 > autoheader && autoconf && ./configure
1090 NAME="NEWRELEASE-AMIGA"
1094 > Ensure that you have the latest code version. Hence run:
1104 CLASS="PROGRAMLISTING"
1105 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1106 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1125 CLASS="PROGRAMLISTING"
1126 > autoheader && autoconf && ./configure
1142 NAME="NEWRELEASE-AIX"
1146 > Login to Sourceforge's compilefarm via ssh:
1156 CLASS="PROGRAMLISTING"
1157 > ssh cf.sourceforge.net
1165 > Choose the right operating system. If you have downloaded Privoxy
1176 CLASS="PROGRAMLISTING"
1177 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1178 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1188 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1191 Privoxy via CVS first</A
1202 CLASS="PROGRAMLISTING"
1203 > autoheader && autoconf && ./configure
1221 CLASS="PROGRAMLISTING"
1230 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
1234 > on the Sourceforge machine (no ncftpput). You now have
1235 to manually upload the archive to Sourceforge's ftp server and release
1280 >Testing Guidelines</TD
1290 >Contacting the developers, Bug Reporting and Feature Requests</TD