X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=55e2f652e6d83a1748492ddfcb2aec4b3e7817b1;hb=56ebceff6dd141235fcfa451427266af29d6fe76;hp=5ff11fb599a716961070ffe48c4db91a3ba18372;hpb=2e43b7767721781355233b72439cb20b01b81a25;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 5ff11fb5..55e2f652 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -4,7 +4,7 @@ >Releasing a New Version
Prev

6. Releasing a New Version

6. Releasing a New Version

When we release versions of

6.1. Version numbers

6.1. Version numbers

First you need to determine which version number the release will have. Y, the version minor, represents the branch within the major version. At any point in time, there are two branches being maintained: The stable branch, with an even minor, say, 2N, in which no functionality is - being added and only bugfixes are made, and 2N+1, the development branch, in + being added and only bug-fixes are made, and 2N+1, the development branch, in which the further development of Privoxy

6.2. Before the Release: Freeze

6.2. Before the Release: Freeze

The following The following must be done by one of the developers prior to each new release.

  • Commit all files that were changed in the above steps!

    • 6.3. Building and Releasing the Packages

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

    For For all types of packages, including the source tarball, - you must make sure that you build from clean sources by exporting the right version from CVS into an empty directory:.

    Do NOT change a single bit, including, but not limited to version information after export from CVS. This is to make sure that all release packages, and with them, all future bug reports, are based @@ -369,14 +379,15 @@ CLASS="SECT3" >

    6.3.1. Note on Privoxy Packaging

    6.3.1. Note on Privoxy Packaging

    Please keep these general guidelines in mind when putting together - your package. These apply to all platforms!

    Privoxy requires write access to: all LICENSE (toplevel directory) +> (top-level directory)

    README (toplevel directory) +> (top-level directory) AUTHORS (toplevel directory) +> (top-level directory) man page (toplevel directory, Unix-like +> (top-level directory, Unix-like platforms only) Developer Manual - (doc/webserver/devel-manual) and ChangeLog - (toplevel directory). FAQ and the manuals are @@ -535,24 +549,31 @@ CLASS="FILENAME" to each other from parallel directories, and should be packaged that way. privoxy-index.html can also be + included and can serve as a focal point for docs and other links of + interest (and possibly renamed to index.html can also be included and - can serve as a focal point for docs and other links of interest. - This should be one level up from the manuals. There are two +>). + This should be one level up from the manuals. There is a link also + on this page to an HTMLized version of the man page. To avoid 404 for + this, it is in CVS as + doc/webserver/man-page/privoxy-man-page.html, + and should be included along with the manuals. There is also a css stylesheets that can be included for better presentation: p_doc.css and . This should be in the same directory + with p_web.css. - These should be in the same directory with - index.html, (i.e. one level up from the manual - directories). +>privoxy-index.html, (i.e. one level up from + the manual directories).

  • 6.3.2. Source Tarball

    6.3.2. Source Tarball

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.3.3. SuSE, Conectiva or Red Hat RPM

    6.3.3. SuSE, Conectiva or Red Hat RPM

    In following text, replace for SuSE.

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above).

    6.3.4. OS/2

    6.3.4. OS/2

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then get the OS/2 Setup module:

    6.3.5. Solaris

    6.3.5. Solaris

    Login to Sourceforge's compilefarm via ssh:

    Choose the right operating system (not the Debian one). - When logged in, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.3.6. Windows

    6.3.6. Windows

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

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then get the Windows setup module:

    • Next
     
            cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetup
    cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetup
            cd winsetup
-        make
    cd winsetup + make

    6.3.7. Debian

    6.3.7. Debian

    First, First, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then, run: -

    make sure that you have freshly exported the + right version into an empty directory. (See + "Building and releasing packages" above). Then add a log + entry to debian/changelog, if it is not + already there, for example by running: + 

      cd current
-  autoheader && autoconf && ./configure
    debchange -v 2.9.15-beta-1 "New upstream version"
    -

    Then do FIXME. -

    Then, run: + 

      dpkg-buildpackage -rfakeroot -us -uc -b
    +

    This will create + ../privoxy_2.9.15-beta-1_i386.deb + which can be uploaded. To upload the package to Sourceforge, simply + issue + 

      make debian-upload
    +

    6.3.8. Mac OSX

    6.3.8. Mac OSX

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then get the Mac OSX setup module: 

    zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
    zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg

    6.3.9. FreeBSD

    6.3.9. FreeBSD

    Login to Sourceforge's compilefarm via ssh: +> Login to Sourceforge's compile-farm via ssh:

    Choose the right operating system. - When logged in, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.3.10. HP-UX 11

    6.3.10. HP-UX 11

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.3.11. Amiga OS

    6.3.11. Amiga OS

    First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.3.12. AIX

    6.3.12. AIX

    Login to Sourceforge's compilefarm via ssh:

    Choose the right operating system. - When logged in, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:

    6.4. Uploading and Releasing Your Package

    6.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 @@ -1540,10 +1613,13 @@ CLASS="LITERAL" of $VERSION ($CODE_STATUS), e.g. , e.g. 2.9.15 (beta).

    6.5. After the Release

    6.5. After the Release

    When all (or: most of the) packages have been uploaded and made available, send an email to the

    Prev
    HomeNext