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";'
186 >Commit all files that were changed in the above steps!</I
192 > Tag all files in CVS with the version number with
200 Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.
205 > The first package uploaded should be the official
209 > release. This is built with the
214 >make tarball-dist</B
217 target, and then can be uploaded with
222 >make tarball-upload</B
236 NAME="NEWRELEASE-WEB"
237 >8.2. Update the webserver</A
240 > All files must be group-readable and group-writable (or no one else
241 will be able to change them). To update the webserver, create any
242 pages locally in the <TT
246 create new directories under <TT
259 CLASS="PROGRAMLISTING"
284 >doc/webserver/user-manual</TT
288 >doc/webserver/developer-manual</TT
292 >doc/webserver/faq</TT
296 >doc/webserver/man-page</TT
300 > Please do NOT use any other means of transferring files to the
308 uploads, but will make sure that the appropriate permissions are
309 preserved for shared group access.
317 NAME="NEWRELEASE-RPM"
318 >8.3. SuSE or Red Hat</A
321 > Ensure that you have the latest code version. Hence run:
331 CLASS="PROGRAMLISTING"
332 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
333 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
352 CLASS="PROGRAMLISTING"
353 > autoheader && autoconf && ./configure
371 CLASS="PROGRAMLISTING"
372 > make suse-dist or make redhat-dist
380 > To upload the package to Sourceforge, simply issue
390 CLASS="PROGRAMLISTING"
391 > make suse-upload or make redhat-upload
399 > Go to the displayed URL and release the file publicly on Sourceforge.
407 NAME="NEWRELEASE-OS2"
411 > Ensure that you have the latest code version. Hence run:
421 CLASS="PROGRAMLISTING"
422 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
423 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
425 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
433 > You will need a mix of development tools.
434 The main compilation takes place with IBM Visual Age C++.
435 Some ancillary work takes place with GNU tools, available from
436 various sources like hobbes.nmsu.edu.
437 Specificially, you will need <TT
448 The packaging takes place with WarpIN, available from various sources, including
450 HREF="http://www.xworkplace.org/"
456 > Change directory to the <TT
460 Edit the os2build.cmd file to set the final executable filename.
469 CLASS="PROGRAMLISTING"
470 > installExeName='privoxyos2_setup_X.Y.Z.exe'
479 > file so the release number matches
491 CLASS="PROGRAMLISTING"
492 > PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
498 You're now ready to build. Run:
506 CLASS="PROGRAMLISTING"
516 > directory you will have the
517 WarpIN-installable executable.
518 Upload this anonymously to
521 >uploads.sourceforge.net/incoming</TT
523 for it, and you're done.
531 NAME="NEWRELEASE-SOLARIS"
535 > Login to Sourceforge's compilefarm via ssh
545 CLASS="PROGRAMLISTING"
546 > ssh cf.sourceforge.net
554 > Choose the right operating system (not the Debian one). If you have
568 CLASS="PROGRAMLISTING"
569 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
570 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
580 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
583 Privoxy via CVS first</A
594 CLASS="PROGRAMLISTING"
595 > autoheader && autoconf && ./configure
613 CLASS="PROGRAMLISTING"
622 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
626 > on the Sourceforge machine (no ncftpput). You now have
627 to manually upload the archive to Sourceforge's ftp server and release
636 NAME="NEWRELEASE-WINDOWS"
640 > Ensure that you have the latest code version. Hence run
650 CLASS="PROGRAMLISTING"
651 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
652 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
671 CLASS="PROGRAMLISTING"
672 > autoheader && autoconf && ./configure
688 NAME="NEWRELEASE-DEBIAN"
692 > Ensure that you have the latest code version. Hence run:
702 CLASS="PROGRAMLISTING"
703 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
704 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
723 CLASS="PROGRAMLISTING"
724 > autoheader && autoconf && ./configure
740 NAME="NEWRELEASE-MACOSX"
744 > Ensure that you have the latest code version. Hence run:
754 CLASS="PROGRAMLISTING"
755 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
756 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
758 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
766 > From the osxsetup directory, run:
774 CLASS="PROGRAMLISTING"
797 Finally, it will copy over the necessary files to the ./osxsetup/files directory
798 for further processing by <TT
804 > Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
805 name to match the release, and hit the "Create package" button.
806 If you specify ./Privoxy.pkg as the output package name, you can then create
807 the distributable zip file with the command:
815 CLASS="PROGRAMLISTING"
816 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
822 You can then upload <TT
824 >privoxyosx_setup_x.y.z.zip</TT
828 >uploads.sourceforge.net/incoming</TT
830 create a release for it, and you're done.
838 NAME="NEWRELEASE-FREEBSD"
842 > Change the version number of <SPAN
846 configure.in file. Run:
854 CLASS="PROGRAMLISTING"
855 > autoheader && autoconf && ./configure
864 > Login to Sourceforge's compilefarm via ssh:
874 CLASS="PROGRAMLISTING"
875 > ssh cf.sourceforge.net
883 > Choose the right operating system.
893 CLASS="PROGRAMLISTING"
894 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
895 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
914 CLASS="PROGRAMLISTING"
915 > autoheader && autoconf && ./configure
933 CLASS="PROGRAMLISTING"
942 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
946 > on the Sourceforge machine (no ncftpput). You now have
947 to manually upload the archive to Sourceforge's ftp server and release
956 NAME="NEWRELEASE-TARBALL"
960 > Ensure that you have the right code version. Hence run:
970 CLASS="PROGRAMLISTING"
971 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
972 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
991 CLASS="PROGRAMLISTING"
992 > autoheader && autoconf && ./configure
1010 CLASS="PROGRAMLISTING"
1019 > To upload the package to Sourceforge, simply issue
1029 CLASS="PROGRAMLISTING"
1030 > make tarball-upload
1038 > Goto the displayed URL and release the file publicly on Sourceforge.
1046 NAME="NEWRELEASE-HPUX"
1050 > Ensure that you have the latest code version. Hence run:
1060 CLASS="PROGRAMLISTING"
1061 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1062 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1081 CLASS="PROGRAMLISTING"
1082 > autoheader && autoconf && ./configure
1098 NAME="NEWRELEASE-AMIGA"
1102 > Ensure that you have the latest code version. Hence run:
1112 CLASS="PROGRAMLISTING"
1113 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1114 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1133 CLASS="PROGRAMLISTING"
1134 > autoheader && autoconf && ./configure
1150 NAME="NEWRELEASE-AIX"
1154 > Login to Sourceforge's compilefarm via ssh:
1164 CLASS="PROGRAMLISTING"
1165 > ssh cf.sourceforge.net
1173 > Choose the right operating system. If you have downloaded Privoxy
1184 CLASS="PROGRAMLISTING"
1185 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1186 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
1196 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1199 Privoxy via CVS first</A
1210 CLASS="PROGRAMLISTING"
1211 > autoheader && autoconf && ./configure
1229 CLASS="PROGRAMLISTING"
1238 > which creates a gzip'ed tar archive. Sadly, you cannot use <B
1242 > on the Sourceforge machine (no ncftpput). You now have
1243 to manually upload the archive to Sourceforge's ftp server and release
1288 >Testing Guidelines</TD
1298 >Contacting the developers, Bug Reporting and Feature Requests</TD