So when releasing a new version, please adhere exactly to the procedure outlined in this chapter.
-The following programs are required to follow this process: ncftpput (ncftp), - scp, ssh (ssh), gmake (GNU's version of make), autoconf, - cvs.
+The following programs are required to follow this process: ssh, gmake (GNU's version of make), autoconf, git, a web browser.
First you need to determine which version number the release will have.
X, the version major, is rarely ever changed. It is increased by one if turning a development branch into
stable substantially changes the functionality, user interface or configuration syntax. Majors 1 and 2 were
- Junkbuster, and 3 will be the first stable Junkbuster, and 3 is the first stable Privoxy release.
The following must be done by one of the developers prior to each new release.
- - $ utils/changelog2doc.pl /tmp/change.log >| doc/source/changelog.sgml+ $ utils/changelog2doc.pl /tmp/change.log >| doc/source/changelog.sgml |
- $ make dok +$ make man + $ make dok + $ make dok-man $ make dok-tidy - $ make man $ make config-file |
mkdir dist # delete or choose different name if it already exists cd dist - cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current+ git clone https://www.privoxy.org/git/privoxy.git + cd privoxy + git checkout v_X_Y_Z |
Then run:
- - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup- |
-
You will need a mix of development tools. The main compilation takes place with IBM Visual Age C++. Some - ancillary work takes place with GNU tools, available from various sources like hobbes.nmsu.edu. Specificially, - you will need autoheader, autoconf and sh tools. The packaging takes place with WarpIN, available from various sources, including its - home page: xworkplace.
-Change directory to the os2setup directory. Edit the os2build.cmd file to set the - final executable filename. For example,
-
- installExeName='privoxyos2_setup_X.Y.Z.exe'- |
-
Next, edit the IJB.wis file so the release number matches in the PACKAGEID section:
-
- PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"- |
-
You're now ready to build. Run:
-
- os2build- |
-
You will find the WarpIN-installable executable in the ./files directory. Upload - this anonymously to uploads.sourceforge.net/incoming, create a release for it, and - you're done. Use the release notes and Change Log from the source tarball package.
-Login to Sourceforge's compilefarm via ssh:
- debchange -v 3.0.27-UNRELEASED-1 "New upstream version"+ debchange -v 3.0.29-stable-1 "New upstream version" |
This will create ../privoxy_3.0.27-UNRELEASED-1_i386.deb which can be uploaded. To +
This will create ../privoxy_3.0.29-stable-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue
First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above).
-There are three modules available in the Git repository for use on Mac OS X, though technically only two of - them generate a release (the other can be used to install from source).
+There are three modules available in the CVS repository backups for use on Mac OS X, though technically only + two of them generate a release (the other can be used to install from source).
The OSXPackageBuilder module generates OS X installer packages supporting all Macs running OS X 10.4 and - above. Obtain it from Git as follows into a folder parallel to the exported privoxy source:
+ above. Obtain it from CVS as follows into a folder parallel to the exported privoxy source:
- - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder |
This module is deprecated since the installer it generates places all Privoxy files in one folder in a non-standard location, and supports only Intel Macs running OS X 10.6 or higher.
-Check out the module from Git as follows into a folder parallel to the exported privoxy source:
+Check out the module from CVS as follows into a folder parallel to the exported privoxy source:
- - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup |
The macsetup module is ideal if you wish to build and install Privoxy from source on a single machine.
-Check out the module from Git as follows into a folder parallel to the exported privoxy source:
+Check out the module from CVS as follows into a folder parallel to the exported privoxy source:
- - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup |
Update the www/privoxy port and submit a diff upstream. For details see the FreeBSD Porter's Handbook.
@@ -674,7 +628,7 @@ for-privoxy-version=3.0.11 "_top">https://sourceforge.net/project/admin/editpackages.php?group_id=11118, making sure you are logged in. Find your target platform in the second column, and click Add Release. You will then need to create a new release for your package, using the format of $VERSION - ($CODE_STATUS), e.g. 3.0.27 (beta). + ($CODE_STATUS), e.g. 3.0.29 (beta).Now just follow the prompts. Be sure to add any appropriate Release notes. You should see your freshly uploaded packages in "Step 2. Add Files To This Release". Check the appropriate box(es). Remember at each step to hit the "Refresh/Submit" buttons! You should now see @@ -689,11 +643,10 @@ for-privoxy-version=3.0.11
When all (or: most of the) packages have been uploaded and made available, send an email to the announce mailing list, Subject: "Version X.Y.Z - available for download". Be sure to include the download location, the release - notes and the Changelog. Also, post an updated News item on the project page Sourceforge, and update the Home - page and docs linked from the Home page (see below). Other news sites and release oriented sites, such as - Freshmeat, should also be notified.
+ available for download". Be sure to include the download location, the release notes and the Changelog. Also, post an updated News item on the project + page Sourceforge, and update the Home page and docs linked from the Home page (see below). Other news sites and + release oriented sites, such as Freshmeat, should also be notified.Then update the source code for the next version to be released: