1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
5 <title>Releasing a New Version</title>
6 <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79">
7 <link rel="HOME" title="Privoxy Developer Manual" href="index.html">
8 <link rel="PREVIOUS" title="Testing Guidelines" href="testing.html">
9 <link rel="NEXT" title="Update the Webserver" href="webserver-update.html">
10 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
11 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
13 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink="#840084" alink="#0000FF">
14 <div class="NAVHEADER">
15 <table summary="Header navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
17 <th colspan="3" align="center">Privoxy Developer Manual</th>
20 <td width="10%" align="left" valign="bottom"><a href="testing.html" accesskey="P">Prev</a></td>
21 <td width="80%" align="center" valign="bottom"></td>
22 <td width="10%" align="right" valign="bottom"><a href="webserver-update.html" accesskey="N">Next</a></td>
25 <hr align="left" width="100%">
28 <h1 class="SECT1"><a name="NEWRELEASE" id="NEWRELEASE">6. Releasing a New Version</a></h1>
29 <p>When we release versions of <span class="APPLICATION">Privoxy</span>, our work leaves our cozy secret lab and
30 has to work in the cold RealWorld[tm]. Once it is released, there is no way to call it back, so it is very
31 important that great care is taken to ensure that everything runs fine, and not to introduce problems in the very
33 <p>So when releasing a new version, please adhere exactly to the procedure outlined in this chapter.</p>
34 <p>The following programs are required to follow this process: <tt class="FILENAME">ssh</tt>, <tt class=
35 "FILENAME">gmake</tt> (GNU's version of make), autoconf, git, a web browser.</p>
37 <h2 class="SECT2"><a name="VERSIONNUMBERS" id="VERSIONNUMBERS">6.1. Version numbers</a></h2>
38 <p>First you need to determine which version number the release will have. <span class=
39 "APPLICATION">Privoxy</span> version numbers consist of three numbers, separated by dots, like in X.Y.Z (e.g.
43 <p>X, the version major, is rarely ever changed. It is increased by one if turning a development branch into
44 stable substantially changes the functionality, user interface or configuration syntax. Majors 1 and 2 were
45 <span class="APPLICATION">Junkbuster</span>, and 3 is the first stable <span class=
46 "APPLICATION">Privoxy</span> release.</p>
49 <p>Y, the version minor, represents the branch within the major version. At any point in time, there are two
50 branches being maintained: The stable branch, with an even minor, say, 2N, in which no functionality is being
51 added and only bug-fixes are made, and 2N+1, the development branch, in which the further development of
52 <span class="APPLICATION">Privoxy</span> takes place. This enables us to turn the code upside down and inside
53 out, while at the same time providing and maintaining a stable version. The minor is reset to zero (and one)
54 when the major is incremented. When a development branch has matured to the point where it can be turned into
55 stable, the old stable branch 2N is given up (i.e. no longer maintained), the former development branch 2N+1
56 becomes the new stable branch 2N+2, and a new development branch 2N+3 is opened.</p>
59 <p>Z, the point or sub version, represents a release of the software within a branch. It is therefore
60 incremented immediately after each software release. The point version is reset to zero when the minor
62 <p>Stable branches work a little differently, since there should be little to no development happening in
63 such branches. Remember, only bugfixes, which presumably should have had some testing before being committed.
64 Stable branches will then have their version reported as <tt class="LITERAL">0.0.0</tt>, during that period
65 between releases when changes are being added. This is to denote that this code is <span class=
66 "emphasis"><i class="EMPHASIS">not for release</i></span>. Then as the release nears, the version is bumped
67 according: e.g. <tt class="LITERAL">3.0.1 -> 0.0.0 -> 3.0.2</tt>.</p>
70 <p>In summary, the main Git trunk is the development branch where new features are being worked on for the next
71 stable series. This should almost always be where the most activity takes place. There is always at least one
72 stable branch from the trunk, e.g now it is <tt class="LITERAL">3.0</tt>, which is only used to release stable
73 versions. Once the initial *.0 release of the stable branch has been done, then as a rule, only bugfixes that
74 have had prior testing should be committed to the stable branch. Once there are enough bugfixes to justify a new
75 release, the version of this branch is again incremented Example: 3.0.0 -> 3.0.1 -> 3.0.2, etc are all
76 stable releases from within the stable branch. 3.1.x is currently the main trunk, and where work on 3.2.x is
77 taking place. If any questions, please post to the devel list <span class="emphasis"><i class=
78 "EMPHASIS">before</i></span> committing to a stable branch!</p>
79 <p>Developers should remember too that if they commit a bugfix to the stable branch, this will more than likely
80 require a separate submission to the main trunk, since these are separate development trees within Git. If you
81 are working on both, then this would require at least two separate check outs (i.e main trunk, <span class=
82 "emphasis"><i class="EMPHASIS">and</i></span> the stable release branch, which is <tt class=
83 "LITERAL">v_3_0_branch</tt> at the moment).</p>
86 <h2 class="SECT2"><a name="BEFORERELEASE" id="BEFORERELEASE">6.2. Before the Release</a></h2>
87 <p>The following <span class="emphasis"><i class="EMPHASIS">must be done by one of the developers</i></span>
88 prior to each new release.</p>
91 <p>Make sure that everybody who has worked on the code in the last couple of days has had a chance to yell
92 <span class="QUOTE">"no!"</span> in case they have pending changes/fixes in their pipelines. Announce the
93 freeze so that nobody will interfere with last minute changes.</p>
96 <p>Update the code status (CODE_STATUS="xxx") in configure.in to one of "alpha", "beta" or "stable".</p>
99 <p>Rebuild configure and GNUMakefile to make sure the updated values are being used.</p>
100 <table border="0" bgcolor="#E0E0E0" width="90%">
103 <pre class="PROGRAMLISTING">$ autoheader && autoconf # rebuild configure
104 $ ./configure # rebuild GNUmakefile</pre>
110 <p><b class="COMMAND">make dok-release</b> to update the sgml documentation source files.</p>
113 <p>If action file processing has changed and is not backward-compatible, make sure the
114 "for-privoxy-version=x.y.z" minimum version number in default.action.master has been updated:</p>
115 <table border="0" bgcolor="#E0E0E0" width="90%">
118 <pre class="PROGRAMLISTING">{{settings}}
119 #############################################################################
120 #MASTER# COMMENT: The minimum Privoxy version:
121 for-privoxy-version=3.0.11</pre>
127 <p>Create the change log:</p>
128 <table border="0" bgcolor="#E0E0E0" width="90%">
131 <pre class="PROGRAMLISTING"> $ git tag
133 $ git log [last release tag]..master > /tmp/log
134 # get the commit log since the last release
135 $ utils/makeChangeLog /tmp/log > /tmp/change.log
136 # reformat the commit log</pre>
140 <p>Edit <tt class="FILENAME">/tmp/change.log</tt> to remove trivial changes and group the changes under
141 general headings like:</p>
142 <table border="0" bgcolor="#E0E0E0" width="90%">
145 <pre class="PROGRAMLISTING">- Bug fixes:
146 - Action file improvements:
147 - Filter file improvements:
148 - General improvements:
149 - Documentation improvements:
150 - Build system improvements:
152 - Privoxy-Log-Parser:
153 - Privoxy-Regression-Test:</pre>
157 <p>Add the contents of <tt class="FILENAME">/tmp/change.log</tt> to the start of <tt class=
158 "FILENAME">ChangeLog</tt> and re-create <tt class="FILENAME">doc/source/changelog.sgml</tt>:</p>
159 <table border="0" bgcolor="#E0E0E0" width="90%">
163 "PROGRAMLISTING"> $ utils/changelog2doc.pl /tmp/change.log >| doc/source/changelog.sgml</pre>
169 <p>All developers should look at the <tt class="FILENAME">ChangeLog</tt> and make sure noteworthy changes are
173 <p>Update the announcement at <tt class="FILENAME">doc/webserver/announce.txt</tt>.</p>
176 <p>All documentation should be rebuilt:</p>
177 <table border="0" bgcolor="#E0E0E0" width="90%">
180 <pre class="PROGRAMLISTING"> $ make man
184 $ make config-file</pre>
187 </table>Finished docs should be then be committed to Git (for those without the ability to build these). Some
188 docs may require rather obscure processing tools. <tt class="FILENAME">config</tt>, the man page (and the
189 html version of the man page) fall in this category. README, the man page, AUTHORS, and config should all
190 also be committed to Git for other packagers. The formal docs should be uploaded to the webserver. See the
191 section <a href="webserver-update.html" target="_top">"Updating the webserver"</a> in this manual for
195 <p><span class="emphasis"><i class="EMPHASIS">Commit all files that were changed in the above
196 steps!</i></span></p>
199 <p>The <i class="CITETITLE">User Manual</i> is also used for context sensitive help for the CGI editor. This
200 is version sensitive, so that the user will get appropriate help for his/her release. So with each release a
201 fresh version should be uploaded to the webserver (this is in addition to the main <i class="CITETITLE">User
202 Manual</i> link from the main page since we need to keep manuals for various versions available). The CGI
203 pages will link to something like <tt class="LITERAL">https://www.privoxy.org/$(VERSION)/user-manual/</tt>.
204 This needs to be updated for each new release and is done with the <span class="QUOTE">"webserver"</span>
208 <p>Tag all files in Git with the version number with <span class="QUOTE">"<b class="COMMAND">git tag -s
209 v_X_Y_Z</b>"</span>. Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.</p>
212 <p>Push the tag to the remote with <span class="QUOTE">"<b class="COMMAND">git push origin
213 v_X_Y_Z</b>"</span>.</p>
216 <p>On the webserver, copy the user manual to a new top-level directory called <tt class=
217 "FILENAME">X.Y.Z</tt>. This ensures that help links from the CGI pages, which have the version as a prefix,
218 will go into the right version of the manual. If this is a development branch release, also symlink
219 <tt class="FILENAME">X.Y.(Z-1)</tt> to <tt class="FILENAME">X.Y.Z</tt> and <tt class=
220 "FILENAME">X.Y.(Z+1)</tt> to <tt class="FILENAME">.</tt> (i.e. dot).</p>
225 <h2 class="SECT2"><a name="THERELEASE" id="THERELEASE">6.3. Building and Releasing the Packages</a></h2>
226 <p>Now the individual packages can be built and released. Note that for GPL reasons the first package to be
227 released is always the source tarball.</p>
228 <p>For <span class="emphasis"><i class="EMPHASIS">all</i></span> types of packages, including the source tarball,
229 <span class="emphasis"><i class="EMPHASIS">you must make sure that you build from clean sources by exporting the
230 right version from Git into an empty directory</i></span> (just press return when asked for a password):</p>
231 <table border="0" bgcolor="#E0E0E0" width="100%">
234 <pre class="PROGRAMLISTING"> mkdir dist # delete or choose different name if it already exists
236 git clone https://www.privoxy.org/git/privoxy.git
238 git checkout v_X_Y_Z</pre>
242 <p><span class="emphasis"><i class="EMPHASIS">Do NOT change</i></span> a single bit, including, but not limited
243 to version information after export from Git. This is to make sure that all release packages, and with them, all
244 future bug reports, are based on exactly the same code.</p>
245 <div class="WARNING">
246 <table class="WARNING" border="1" width="100%">
248 <td align="center"><b>Warning</b></td>
252 <p>Every significant release of Privoxy has included at least one package that either had incorrect
253 versions of files, missing files, or incidental leftovers from a previous build process that gave unknown
254 numbers of users headaches to try to figure out what was wrong. PLEASE, make sure you are using pristene
255 sources, and are following the prescribed process!</p>
260 <p>Please find additional instructions for the source tarball and the individual platform dependent binary
261 packages below. And details on the Sourceforge release process below that.</p>
263 <h3 class="SECT3"><a name="PACK-GUIDELINES" id="PACK-GUIDELINES">6.3.1. Note on Privoxy Packaging</a></h3>
264 <p>Please keep these general guidelines in mind when putting together your package. These apply to <span class=
265 "emphasis"><i class="EMPHASIS">all</i></span> platforms!</p>
268 <p><span class="APPLICATION">Privoxy</span> <span class="emphasis"><i class="EMPHASIS">requires</i></span>
269 write access to: all <tt class="FILENAME">*.action</tt> files, all logfiles, and the <tt class=
270 "FILENAME">trust</tt> file. You will need to determine the best way to do this for your platform.</p>
273 <p>Please include up to date documentation. At a bare minimum:</p>
277 <td><tt class="FILENAME">LICENSE</tt> (top-level directory)</td>
284 <td><tt class="FILENAME">README</tt> (top-level directory)</td>
291 <td><tt class="FILENAME">AUTHORS</tt> (top-level directory)</td>
298 <td><tt class="FILENAME">man page</tt> (top-level directory, Unix-like platforms only)</td>
305 <td><tt class="FILENAME">The User Manual</tt> (doc/webserver/user-manual/)</td>
312 <td><tt class="FILENAME">FAQ</tt> (doc/webserver/faq/)</td>
316 <p>Also suggested: <tt class="FILENAME">Developer Manual</tt> (doc/webserver/developer-manual) and
317 <tt class="FILENAME">ChangeLog</tt> (top-level directory). <tt class="FILENAME">FAQ</tt> and the manuals
319 <p>The documentation has been designed such that the manuals are linked to each other from parallel
320 directories, and should be packaged that way. <tt class="FILENAME">privoxy-index.html</tt> can also be
321 included and can serve as a focal point for docs and other links of interest (and possibly renamed to
322 <tt class="FILENAME">index.html</tt>). This should be one level up from the manuals. There is a link also
323 on this page to an HTMLized version of the man page. To avoid 404 for this, it is in Git as <tt class=
324 "FILENAME">doc/webserver/man-page/privoxy-man-page.html</tt>, and should be included along with the
325 manuals. There is also a css stylesheets that can be included for better presentation: <tt class=
326 "FILENAME">p_doc.css</tt>. This should be in the same directory with <tt class=
327 "FILENAME">privoxy-index.html</tt>, (i.e. one level up from the manual directories).</p>
330 <p><tt class="FILENAME">user.action</tt> and <tt class="FILENAME">user.filter</tt> are designed for local
331 preferences. Make sure these do not get overwritten! <tt class="FILENAME">config</tt> should not be
332 overwritten either. This has especially important configuration data in it. <tt class="FILENAME">trust</tt>
333 should be left in tact as well.</p>
336 <p>Other configuration files (<tt class="FILENAME">default.action</tt>, <tt class=
337 "FILENAME">regression-tests.action</tt> and <tt class="FILENAME">default.filter</tt>) should be installed
338 as the new defaults, but all previously installed configuration files should be preserved as backups. This
339 is just good manners :-) These files are likely to change between releases and contain important new
340 features and bug fixes.</p>
343 <p>Please check platform specific notes in this doc, if you haven't done <span class=
344 "QUOTE">"Privoxy"</span> packaging before for other platform specific issues. Conversely, please add any
345 notes that you know are important for your platform (or contact one of the doc maintainers to do this if
349 <p>Packagers should do a <span class="QUOTE">"clean"</span> install of their package after building it. So
350 any previous installs should be removed first to ensure the integrity of the newly built package. Then run
351 the package for a while to make sure there are no obvious problems, before uploading.</p>
356 <h3 class="SECT3"><a name="NEWRELEASE-TARBALL" id="NEWRELEASE-TARBALL">6.3.2. Source Tarball</a></h3>
357 <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that you have freshly exported the right version
358 into an empty directory</i></span>. (See "Building and releasing packages" above). Then run from that
360 <table border="0" bgcolor="#E0E0E0" width="100%">
363 <pre class="PROGRAMLISTING"> autoheader && autoconf && ./configure</pre>
368 <table border="0" bgcolor="#E0E0E0" width="100%">
371 <pre class="PROGRAMLISTING"> make tarball-dist</pre>
377 <h3 class="SECT3"><a name="NEWRELEASE-WINDOWS" id="NEWRELEASE-WINDOWS">6.3.3. Windows</a></h3>
378 <p>Note that the docbook generated files might need some hand editing, so the Windows build makefile does not
379 rebuild the docs.</p>
380 <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that you have freshly exported the right version
381 into an empty directory</i></span>. (See "Building and releasing packages" above).</p>
382 <p>Then you can build the package. This is fully automated, and is controlled by <tt class=
383 "FILENAME">windows/GNUmakefile</tt>. All you need to do is:</p>
384 <table border="0" bgcolor="#E0E0E0" width="100%">
387 <pre class="PROGRAMLISTING"> cd windows
392 <p>Now you can manually rename <tt class="FILENAME">privoxy_setup.exe</tt> to <tt class=
393 "FILENAME">privoxy_setup_X.Y.Z.exe</tt>, and the <tt class="FILENAME">build</tt> directory to <tt class=
394 "FILENAME">privoxy_X.Y.Z</tt>. Create a .zip file of the newly renamed <tt class="FILENAME">privoxy_X.Y.Z</tt>
395 directory, GPG sign the installer and zip file,</p>
396 <table border="0" bgcolor="#E0E0E0" width="100%">
399 <pre class="PROGRAMLISTING"> $ gpg --armor --detach --sign <tt class=
400 "FILENAME">privoxy_setup_X.Y.Z.exe</tt>
401 $ gpg --armor --detach --sign <tt class="FILENAME">privoxy_X.Y.Z.zip</tt></pre>
405 <p>and upload the files to SourceForge.</p>
406 <p>When releasing the package on SourceForge, use the release notes and Change Log from the source tarball
410 <h3 class="SECT3"><a name="NEWRELEASE-DEBIAN" id="NEWRELEASE-DEBIAN">6.3.4. Debian</a></h3>
411 <p>Using git-buildpackage we start with a clone of the last Debian version:</p>
412 <table border="0" bgcolor="#E0E0E0" width="100%">
415 <pre class="PROGRAMLISTING"> gbp clone https://salsa.debian.org/debian/privoxy.git
420 <p>or if the repository is already there</p>
421 <table border="0" bgcolor="#E0E0E0" width="100%">
424 <pre class="PROGRAMLISTING"> cd privoxy
429 <p>Now import the newly released upstream tarball via debian/watch file:</p>
430 <table border="0" bgcolor="#E0E0E0" width="100%">
433 <pre class="PROGRAMLISTING"> gbp import-orig --uscan</pre>
437 <p>Next update all Debian quilt patches to the new version:</p>
438 <table border="0" bgcolor="#E0E0E0" width="100%">
441 <pre class="PROGRAMLISTING"> while quilt push; do quilt refresh; done</pre>
445 <p>If some patch is no longer required (because it is already merged upstream), it can be removed using</p>
446 <table border="0" bgcolor="#E0E0E0" width="100%">
449 <pre class="PROGRAMLISTING"> quilt delete XX_patchname.patch
450 git rm debian/patches/XX_patchname.patch</pre>
454 <p>If the patch needs modification, you can apply, edit and update it with</p>
455 <table border="0" bgcolor="#E0E0E0" width="100%">
458 <pre class="PROGRAMLISTING"> quilt push -f
465 <table border="0" bgcolor="#E0E0E0" width="100%">
468 <pre class="PROGRAMLISTING"> while quilt push; do quilt refresh; done</pre>
472 <p>succeeds. Then you can</p>
473 <table border="0" bgcolor="#E0E0E0" width="100%">
476 <pre class="PROGRAMLISTING"> quilt pop -a</pre>
480 <p>Now add a new entry to the debian/changelog representing the new version:</p>
481 <table border="0" bgcolor="#E0E0E0" width="100%">
484 <pre class="PROGRAMLISTING"> dch -v 3.0.33-1</pre>
488 <p>and describe what you did before and don't forget to git commit all changes.</p>
489 <p>Now you can build the package on the local machine using</p>
490 <table border="0" bgcolor="#E0E0E0" width="100%">
493 <pre class="PROGRAMLISTING"> gbp buildpackage -us -uc</pre>
497 <p>You should check for warnings using</p>
498 <table border="0" bgcolor="#E0E0E0" width="100%">
501 <pre class="PROGRAMLISTING"> lintian -iI ../build-area/privoxy_3.0.33-1_amd64.changes</pre>
505 <p>Maybe rebuild the package in different defined cowbuilder environments like</p>
506 <table border="0" bgcolor="#E0E0E0" width="100%">
510 "PROGRAMLISTING"> sudo cowbuilder --build --basepath /var/cache/pbuilder/base.cow ../build-area/privoxy_3.0.33-1.dsc</pre>
514 <p>And try to run autopackage testing suite on the result:</p>
515 <table border="0" bgcolor="#E0E0E0" width="100%">
519 "PROGRAMLISTING"> autopkgtest /var/cache/pbuilder/result/privoxy_3.0.33-1_amd64.changes -s -- schroot sid</pre>
523 <p>Or just push the changes to salsa.debian.org, where a CI pipeline is defined for the package, that builds
525 <p>If everything is okay, run cowbuilder with i386 and amd64 environments for current Debian stable release and
526 build privoxy_3.0.33-1_i386.deb and privoxy_3.0.33-1_amd64.deb. Then sign both files:</p>
527 <table border="0" bgcolor="#E0E0E0" width="100%">
530 <pre class="PROGRAMLISTING"> gpg --detach-sign --armor privoxy_3.0.33-1_i386.deb
531 gpg --detach-sign --armor privoxy_3.0.33-1_amd64.deb</pre>
535 <p>Create a README file containing the recent block from debian/changelog and upload the two packages, the two
536 signatures and the README to a freshly created folder below
537 https://sourceforge.net/projects/ijbswa/files/Debian/</p>
539 <h4 class="SECT4"><a name="SNAPSHOT-DEBIAN" id="SNAPSHOT-DEBIAN">6.3.4.1. Debian GIT Snapshot</a></h4>
540 <p>For building just a git snapshot build the following workflow may be useful. First create a build
541 environment, for this you may have to run the following commands:</p>
542 <table border="0" bgcolor="#E0E0E0" width="100%">
545 <pre class="PROGRAMLISTING"> sudo apt install build-essential devscripts
546 sudo apt-get build-dep privoxy</pre>
550 <p>After this enter the checked out privoxy git tree and check that all (new) build dependencies are met:</p>
551 <table border="0" bgcolor="#E0E0E0" width="100%">
554 <pre class="PROGRAMLISTING"> dpkg-checkbuilddeps</pre>
558 <p>If something is missing, just add it using</p>
559 <table border="0" bgcolor="#E0E0E0" width="100%">
562 <pre class="PROGRAMLISTING"> sudo apt install foobar</pre>
566 <p>Now you may update debian/changelog, especially the version number using</p>
567 <table border="0" bgcolor="#E0E0E0" width="100%">
570 <pre class="PROGRAMLISTING"> dch</pre>
574 <p>and finally build the package:</p>
575 <table border="0" bgcolor="#E0E0E0" width="100%">
578 <pre class="PROGRAMLISTING"> debuild -us -uc -b</pre>
582 <p>If everything went okay, you may find the resulting Debian package in the parent directory.</p>
583 <p>You may want to clean up the build tree using</p>
584 <table border="0" bgcolor="#E0E0E0" width="100%">
587 <pre class="PROGRAMLISTING"> debian/rules clean</pre>
591 <p>And maybe repair some artefacts using one or both of the following commands:</p>
592 <table border="0" bgcolor="#E0E0E0" width="100%">
595 <pre class="PROGRAMLISTING"> git reset --hard
603 <h3 class="SECT3"><a name="NEWRELEASE-MACOSX" id="NEWRELEASE-MACOSX">6.3.5. Mac OS X</a></h3>
604 <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that you have freshly exported the right version
605 into an empty directory</i></span>. (See "Building and releasing packages" above).</p>
606 <p>There are three modules available in the CVS repository backups for use on Mac OS X, though technically only
607 two of them generate a release (the other can be used to install from source).</p>
609 <h4 class="SECT4"><a name="OS-X-OSXPACKAGEBUILDER-MODULE" id="OS-X-OSXPACKAGEBUILDER-MODULE">6.3.5.1.
610 OSXPackageBuilder module (Documentation out of date)</a></h4>
611 <p>The OSXPackageBuilder module generates OS X installer packages supporting all Macs running OS X 10.4 and
612 above. Obtain it from CVS as follows into a folder parallel to the exported privoxy source:</p>
613 <table border="0" bgcolor="#E0E0E0" width="100%">
617 "PROGRAMLISTING"> cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder</pre>
621 <p>The module contains complete instructions on its usage in the file <tt class="FILENAME">OS X Package
622 Builder HOWTO.txt</tt>.</p>
623 <p>Once the package(s) have been generated, you can then upload them directly to the Files section of the
624 Sourceforge project in the Macintosh (OS X) folder. Each new version release of Privoxy should have a new
625 subfolder created in which to store its files. Please ensure that the folder contains a readme file that
626 makes it clear which package is for whichversion of OS X.</p>
629 <h4 class="SECT4"><a name="OS-X-OSXSETUP-MODULE" id="OS-X-OSXSETUP-MODULE">6.3.5.2. osxsetup module
630 (DEPRECATED) (Documentation out of date)</a></h4>
631 <p><span class="emphasis"><i class="EMPHASIS">This module is deprecated since the installer it generates
632 places all Privoxy files in one folder in a non-standard location, and supports only Intel Macs running OS X
633 10.6 or higher.</i></span></p>
634 <p>Check out the module from CVS as follows into a folder parallel to the exported privoxy source:</p>
635 <table border="0" bgcolor="#E0E0E0" width="100%">
639 "PROGRAMLISTING"> cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup</pre>
644 <table border="0" bgcolor="#E0E0E0" width="100%">
647 <pre class="PROGRAMLISTING"> cd osxsetup
652 <p>This will run <tt class="FILENAME">autoheader</tt>, <tt class="FILENAME">autoconf</tt> and <tt class=
653 "FILENAME">configure</tt> as well as <tt class="FILENAME">make</tt>. Finally, it will copy over the necessary
654 files to the ./osxsetup/files directory for further processing by <tt class="FILENAME">PackageMaker</tt>.</p>
655 <p>Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package name to match the
656 release, and hit the "Create package" button. If you specify ./Privoxy.pkg as the output package name, you
657 can then create the distributable zip file with the command:</p>
658 <table border="0" bgcolor="#E0E0E0" width="100%">
661 <pre class="PROGRAMLISTING"> zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg</pre>
665 <p>You can then upload this file directly to the Files section of the Sourceforge project in the Macintosh
666 (OS X) folder. Each new version release of Privoxy should have a new subfolder created in which to store its
667 files. Please ensure that the folder contains a readme file that makes it clear which version(s) of OS X the
668 package supports.</p>
671 <h4 class="SECT4"><a name="OS-X-MACSETUP-MODULE" id="OS-X-MACSETUP-MODULE">6.3.5.3. macsetup module
672 (Documentation out of date)</a></h4>
673 <p>The macsetup module is ideal if you wish to build and install Privoxy from source on a single machine.</p>
674 <p>Check out the module from CVS as follows into a folder parallel to the exported privoxy source:</p>
675 <table border="0" bgcolor="#E0E0E0" width="100%">
679 "PROGRAMLISTING"> cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup</pre>
683 <p>The module contains complete instructions on its usage in its <tt class="FILENAME">README</tt> file. The
684 end result will be the exported version of Privoxy installed on the build machine.</p>
688 <h3 class="SECT3"><a name="NEWRELEASE-FREEBSD" id="NEWRELEASE-FREEBSD">6.3.6. FreeBSD</a></h3>
689 <p>Update the www/privoxy port and submit a diff upstream. For details see the <a href=
690 "https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/" target="_top">FreeBSD Porter's
695 <h2 class="SECT2"><a name="RELEASING" id="RELEASING">6.4. Uploading and Releasing Your Package</a></h2>
696 <p>After the package is ready, it is time to upload it and go through the release steps. The upload is done at
697 <a href="https://sourceforge.net/projects/ijbswa/upload/" target="_top">SourceForge</a> after logging in.</p>
698 <p>Now just follow the prompts. Be sure to add any appropriate Release notes. You should see your freshly
699 uploaded packages in <span class="QUOTE">"Step 2. Add Files To This Release"</span>. Check the appropriate
700 box(es). Remember at each step to hit the <span class="QUOTE">"Refresh/Submit"</span> buttons! You should now see
701 your file(s) listed in Step 3. Fill out the forms with the appropriate information for your platform, being sure
702 to hit <span class="QUOTE">"Update"</span> for each file. If anyone is monitoring your platform, check the
703 <span class="QUOTE">"email"</span> box at the very bottom to notify them of the new package. This should do
705 <p>If you have made errors, or need to make changes, you can go through essentially the same steps, but select
706 <tt class="LITERAL">Edit Release</tt>, instead of <tt class="LITERAL">Add Release</tt>.</p>
709 <h2 class="SECT2"><a name="AFTERRELEASE" id="AFTERRELEASE">6.5. After the Release</a></h2>
710 <p>When all (or: most of the) packages have been uploaded and made available, send an email to the <a href=
711 "mailto:privoxy-announce@lists.privoxy.org" target="_top">announce mailing list</a>, Subject: "Announcing Privoxy
712 X.Y.Z $CODE_STATUS". Be sure to include the <a href="https://sourceforge.net/projects/ijbswa/files/" target=
713 "_top">download location</a>, the release notes and the Changelog. Also, post an updated News item on the project
714 page Sourceforge, and update the Home page and docs linked from the Home page (see below). Other news sites and
715 release oriented sites, such as Freshmeat, should also be notified.</p>
716 <p>Then update the source code for the next version to be released:</p>
719 <p>Increment the version number and change the code status to "UNRELEASED" in <tt class=
720 "FILENAME">configure.in</tt></p>
723 <p>Rebuild configure (<span class="QUOTE">"<b class="COMMAND">autoheader && autoconf</b>"</span>) and
724 GNUMakefile (<span class="QUOTE">"<b class="COMMAND">./configure</b>"</span>)</p>
727 <p><span class="QUOTE">"<b class="COMMAND">make dok-release</b>"</span> to update the sgml documentation
731 <p>Commit all your changes.</p>
736 <div class="NAVFOOTER">
737 <hr align="left" width="100%">
738 <table summary="Footer navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
740 <td width="33%" align="left" valign="top"><a href="testing.html" accesskey="P">Prev</a></td>
741 <td width="34%" align="center" valign="top"><a href="index.html" accesskey="H">Home</a></td>
742 <td width="33%" align="right" valign="top"><a href="webserver-update.html" accesskey="N">Next</a></td>
745 <td width="33%" align="left" valign="top">Testing Guidelines</td>
746 <td width="34%" align="center" valign="top"> </td>
747 <td width="33%" align="right" valign="top">Update the Webserver</td>