X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=38ec2d50286bb6b97179a359ce4ee6822853f638;hb=016253d925d92fe8770ad306bb84c14ff8b1027e;hp=a9c3b3e785822801686fa03132078f1008d50f1b;hpb=72081f829de368392d04076728f8c991178c0080;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index a9c3b3e7..38ec2d50 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -1,11 +1,11 @@ - Releasing a New Version6. Releasing a New Version6. Releasing a New Version

When we release versions of 6.1. Version numbers6.1. Version numbers

First you need to determine which version number the release will have. 0.0.00.0.0, during that period between releases when changes are being added. This is to denote that this code is . Then as the release nears, the version is bumped according: e.g. - 3.0.1 -> 0.0.0 -> 3.0.23.0.1 -> 0.0.0 -> 3.0.2.

3.03.0, which is only used to release stable versions. Once the initial *.0 release of the stable branch has been done, then as a rule, only bugfixes that have had prior testing should be committed to @@ -232,9 +232,9 @@ CLASS="EMPHASIS" >and the stable release branch, - which is v_3_0_branchv_3_0_branch at the moment).

6.2. Before the Release: Freeze6.2. Before the Release: Freeze

The following 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/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. @@ -429,8 +429,8 @@ CLASS="SECT2" CLASS="SECT2" >6.3. Building and Releasing the Packages6.3. Building and Releasing the Packages

Now the individual packages can be built and released. Note that for GPL reasons the first package to be released is always the source tarball. @@ -464,8 +464,8 @@ WIDTH="100%" CLASS="PROGRAMLISTING" > mkdir dist # delete or choose different name if it already exists cd dist - cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current

Warning

Every significant release of Privoxy has included at least one + package that either had incorrect versions of files, missing files, + or incidental leftovers from a previous build process that gave + unknown numbers of users headaches to try to figure out what was + wrong. PLEASE, make sure you are using pristene sources, and are + following the prescribed process! +

Please find additional instructions for the source tarball and the individual platform dependent binary packages below. And details @@ -494,8 +524,8 @@ CLASS="SECT3" CLASS="SECT3" >6.3.1. Note on Privoxy Packaging6.3.1. Note on Privoxy Packaging

Please keep these general guidelines in mind when putting together your package. These apply to user.action is designed for local preferences. - Make sure this does not get overwritten! +> and user.filter + are designed for local preferences. Make sure these do not get overwritten! + config should not be overwritten either. This + has especially important configuration data in it. + trust should be left in tact as well.

  • Other configuration files should be installed as the new defaults, - but all previously installed configuration files should be preserved - as backups. This is just good manners :-) +> Other configuration files (default.action, + default.filter and + standard.action) should be installed as the new + defaults, but all previously installed configuration files should be + preserved as backups. This is just good manners :-) These files are + likely to change between releases and contain important new features + and bug fixes.

  • 6.3.2. Source Tarball6.3.2. Source Tarball

    First, 6.3.3. SuSE, Conectiva or Red Hat RPM6.3.3. SuSE, Conectiva or Red Hat RPM

    In following text, replace In following text, replace distdist with either privoxy-distdist.specdistdist which is built from version X.Y.Z. Check the 

      make   make distdist-dist
      make   make dist-upload dist-upload rpm_packagerevrpm_packagerev

    where where rpm_packagerevrpm_packagerev is the RPM release number as determined above. Go to the displayed URL and release the file publicly on Sourceforge. @@ -956,8 +1025,8 @@ CLASS="SECT3" CLASS="SECT3" >6.3.4. OS/26.3.4. OS/2

    First, 

      cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
    cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup6.3.5. Solaris6.3.5. Solaris

    Login to Sourceforge's compilefarm via ssh:

    6.3.6. Windows6.3.6. Windows

    You should ensure you have the latest version of Cygwin (from 

      cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetup
    cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co winsetup6.3.7. Debian6.3.7. Debian

    First, 

      debchange -v 3.0.3-stable-1 "New upstream version"
    debchange -v 3.0.5-BETA-1 "New upstream version" This will create ../privoxy_3.0.3-stable-1_i386.deb../privoxy_3.0.5-BETA-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue @@ -1338,8 +1407,8 @@ CLASS="SECT3" CLASS="SECT3" >6.3.8. Mac OSX6.3.8. Mac OSX

    First, 

      cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
    cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup6.3.9. FreeBSD6.3.9. FreeBSD

    Login to Sourceforge's compile-farm via ssh:

    6.3.10. HP-UX 116.3.10. HP-UX 11

    First, 6.3.11. Amiga OS6.3.11. Amiga OS

    First, 6.3.12. AIX6.3.12. AIX

    Login to Sourceforge's compilefarm via ssh:

    6.4. Uploading and Releasing Your Package6.4. Uploading and Releasing Your Package

    After the package is ready, it is time to upload it to SourceForge, and go through the release steps. The upload @@ -1713,17 +1782,17 @@ TARGET="_top" >

  • user: user: anonymousanonymous

  • password: password: ijbswa-developers@lists.sourceforge.netijbswa-developers@lists.sourceforge.net

    • http://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 ReleaseAdd Release. You will then need to create a new release for your package, using the format - of $VERSION ($CODE_STATUS)$VERSION ($CODE_STATUS), e.g. 3.0.3 +>3.0.5 (beta). @@ -1786,13 +1855,13 @@ CLASS="QUOTE"

    If you have made errors, or need to make changes, you can go through - essentially the same steps, but select Edit ReleaseEdit Release, - instead of Add ReleaseAdd Release.

    6.5. After the Release6.5. After the Release

    When all (or: most of the) packages have been uploaded and made available, send an email to the , 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). + page and docs linked from the Home page (see below). Other news sites + and release oriented sites, such as Freshmeat, should also be notified.