X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=6814b0eabbda4cd386f8c5d57dbfdccebe98c1b2;hb=1e5dbf87271fb9afca4ccd18a19c42e6d4d80dea;hp=6df000e1ef709066271cf7128b55c4666a57671f;hpb=c5aed82a9a4d52c7f44885058167a6e402815226;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 6df000e1..6814b0ea 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -1,11 +1,11 @@ +
Next | 8. Releasing a New Version6. Releasing a New Version
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 on exactly the same code.
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. + individual platform dependent binary packages below. And details + on the Sourceforge release process below that.
Please keep these general guidelines in mind when putting together + your package. These apply to all platforms! +
Privoxy requires + write access to: all *.action files, all + logfiles, and the trust file. You will + need to determine the best way to do this for your platform. +
Please include up to date documentation. At a bare minimum: +
LICENSE (top-level directory) + |
README (top-level directory) + |
AUTHORS (top-level directory) + |
man page (top-level directory, Unix-like + platforms only) + |
The User Manual (doc/webserver/user-manual/) + |
FAQ (doc/webserver/faq/) + |
Also suggested: Developer Manual + (doc/webserver/developer-manual) and ChangeLog + (top-level directory). FAQ and the manuals are + HTML docs. There are also text versions in + doc/text/ which could conceivably also be + included. +
The documentation has been designed such that the manuals are linked + 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). + 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. This should be in the same directory + with privoxy-index.html, (i.e. one level up from + the manual directories). +
user.action 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 (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. +
Please check platform specific notes in this doc, if you haven't + done "Privoxy" packaging before for other platform + specific issues. Conversely, please add any notes that you know + are important for your platform (or contact one of the doc + maintainers to do this if you can't). +
Packagers should do a "clean" install of their + package after building it. So any previous installs should be + removed first to ensure the integrity of the newly built package. + Then run the package for a while to make sure there are no + obvious problems, before uploading. +
First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:
8.2.2. SuSE or Red Hat6.3.3. SuSE, Conectiva or Red Hat RPMFirst, In following text, replace dist + with either "rh" for Red Hat or "suse" for SuSE. +
First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing - packages" above). Then run: + packages" above). +
As the only exception to not changing anything after export from CVS, + now examine the file privoxy-dist.spec + and make sure that the version information and the RPM release number are + correct. The RPM release numbers for each version start at one. Hence it must + be reset to one if this is the first RPM for + dist which is built from version + X.Y.Z. Check the + file + list if unsure. Else, it must be set to the highest already available RPM + release number for that version plus one. +
Then run:
make suse-dist (or make redhat-dist)make dist-dist |
make suse-upload (or make redhat-upload)make dist-upload rpm_packagerev
Go to the displayed URL and release the file publicly on Sourceforge. - Use the release notes and çhange log from the source tarball package. +> where rpm_packagerev is the + RPM release number as determined above. + Go to the displayed URL and release the file publicly on Sourceforge. + Use the release notes and change log from the source tarball package.
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:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup
Login to Sourceforge's compilefarm via ssh: @@ -572,10 +1183,13 @@ CLASS="PROGRAMLISTING"
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:
8.2.5. Windows6.3.6. WindowsYou should ensure you have the latest version of Cygwin (from @@ -642,10 +1256,13 @@ TARGET="_top" Run the following commands from within a Cygwin bash shell.
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:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co winsetup
cd winsetup - makecd winsetup + make
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 && ./configuredebchange -v 3.0.11-stable-1 "New upstream version" |
Then do FIXME. -
Then, run: +
dpkg-buildpackage -rfakeroot -us -uc -b |
This will create + ../privoxy_3.0.11-stable-1_i386.deb + which can be uploaded. To upload the package to Sourceforge, simply + issue +
make debian-upload |
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: + packages" above). Then get the Mac OS X setup module:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup |
zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkgzip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
Login to Sourceforge's compilefarm via ssh: +> Login to Sourceforge's compile-farm via ssh:
Home | Next |