X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=7d4ed88a18b6ea4071e6fed9978540aaa78bee15;hp=ac3a9bef497478477006c2d6a74b3043a45b823e;hb=46471693916537291afcf7eadd40e6b93277bfaa;hpb=5201d451da531cc0997d70bc0b85569771605129 diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index ac3a9bef..7d4ed88a 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -31,9 +31,8 @@ important that great care is taken to ensure that everything runs fine, and not to introduce problems in the very last minute.

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.

6.1. Version numbers

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.

  • @@ -198,9 +197,9 @@ for-privoxy-version=3.0.11 is version sensitive, so that the user will get appropriate help for his/her release. So with each release a fresh version should be uploaded to the webserver (this is in addition to the main User Manual link from the main page since we need to keep manuals for various versions available). The CGI - pages will link to something like http://privoxy.org/$(VERSION)/user-manual/. This - will need to be updated for each new release. There is no Makefile target for this at this time!!! It needs - to be done manually.

    + pages will link to something like https://www.privoxy.org/$(VERSION)/user-manual/. + This will need to be updated for each new release. There is no Makefile target for this at this time!!! It + needs to be done manually.

  • Tag all files in Git with the version number with "git tag @@ -520,13 +519,13 @@ for-privoxy-version=3.0.11

    6.3.7. Mac OS X

    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).

    6.3.7.1. - OSXPackageBuilder module

    + OSXPackageBuilder module (Documentation out of date)

    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:

    @@ -544,11 +543,11 @@ for-privoxy-version=3.0.11

    6.3.7.2. osxsetup module - (DEPRECATED)

    + (DEPRECATED) (Documentation out of date)

    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:

    @@ -585,9 +584,10 @@ for-privoxy-version=3.0.11 package supports.

    -

    6.3.7.3. macsetup module

    +

    6.3.7.3. macsetup module + (Documentation out of date)

    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: