X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=4c5db45498e1b63e6880eadf694add6c45a3bdf9;hp=a9c3b3e785822801686fa03132078f1008d50f1b;hb=2d4220ee5eb5a555f4d9f93fcb4ceac3a0ea379b;hpb=72081f829de368392d04076728f8c991178c0080 diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index a9c3b3e7..4c5db454 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -1,11 +1,11 @@ - + Releasing a New Version0.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 +235,9 @@ CLASS="EMPHASIS" >and the stable release branch, - which is v_3_0_branchv_3_0_branch at the moment).

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. @@ -464,8 +467,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 @@ -697,15 +730,36 @@ CLASS="FILENAME" > 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 and + default.filter) 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.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. @@ -978,7 +1046,7 @@ WIDTH="100%" >

      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 os2setup
      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 winsetup
      debchange -v 3.0.3-stable-1 "New upstream version"
    debchange -v 3.0.17-stable-1 "New upstream version" This will create ../privoxy_3.0.3-stable-1_i386.deb../privoxy_3.0.17-stable-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue @@ -1338,7 +1406,7 @@ CLASS="SECT3" CLASS="SECT3" >    6.3.8. Mac OSX6.3.8. Mac OS X

    First, . (See "Building and releasing - packages" above). Then get the Mac OSX setup module: + packages" above). Then get the Mac OS X setup module: 

      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 osxsetup

  • user: user: anonymousanonymous

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

    • Once this done go to http://sourceforge.net/project/admin/editpackages.php?group_id=11118https://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.17 (beta). @@ -1786,13 +1854,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.

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