*
* Purpose : README file to give a short intro.
*
- * Copyright : Written by and Copyright (C) 2001-2007 the SourceForge
+ * Copyright : Written by and Copyright (C) 2001-2009 the SourceForge
* Privoxy team. http://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
*
*********************************************************************/
-This README is included with the development version of Privoxy 3.0.7. See
+This README is included with the development version of Privoxy 3.0.12. See
http://www.privoxy.org/ for more information. The current code maturity level
-is "beta", but seems stable to us :).
+is "UNRELEASED", but seems stable to us :).
-------------------------------------------------------------------------------
1. IMPORTANT CHANGES
-December 2007, Privoxy 3.0.7 beta is released. This is a significant upgrade
-with many new and enhanced features, and many bugs fixed. See the "ChangeLog",
+Privoxy is between releases. The current code base should be considered
+development quality. Please report any problems to the developers.
+
+February 2009, Privoxy 3.0.11 is released.
+
+As usual there are changes that effect the configuration. See the "ChangeLog",
and the "What's New" section and the "Upgrader's Notes" in the User Manual for
-details and specifics. There are changes related to configuration, so anyone
-upgrading and keeping their old configuration should read ahead first.
+details and specifics.
-NEWS! November 2006, Privoxy 3.0.6 stable is released. This is a significant
-upgrade with many new and enhanced features, and many bugs fixed.
+This is a stable release, and marks a departure for Privoxy development.
-There was and will not be an official 3.0.4 release. This release cycle was
-used to gather our thoughts, play with some new ideas and refine some old ones.
-It will remain a development cycle with no actual release. 3.0.5 is the fruit
-of these efforts.
+Previously, odd numbered releases were considered beta versions and were only
+released at the end of the development cycle when the code was already believed
+to be stable. Usually it was, so the stable release contained pretty much the
+same code, but got a higher version number. In the future we intend to release
+several snapshots between stable releases. There will probably still be about
+two stable releases per year, but hopefully about six snapshots instead of the
+two betas we have now. The intentions is to make testing without CVS access
+easier.
-------------------------------------------------------------------------------
3. RUN
-privoxy [??help] [??version] [??no-daemon] [??pidfile PIDFILE] [??user USER
-[.GROUP]] [??chroot] [??pre?chroot?nslookup HOSTNAME ][config_file]
+privoxy [--help] [--version] [--no-daemon] [--pidfile PIDFILE] [--user USER
+[.GROUP]] [--chroot] [--pre-chroot-nslookup HOSTNAME ][config_file]
See the man page or User Manual for an explanation of each option, and other
configuration and usage issues.
Or for Red Hat and Fedora based distributions: /etc/rc.d/init.d/privoxy start
-Or Debian: /etc/init.d/privoxy start
+Or Debian and Ubuntu: /etc/init.d/privoxy start
-------------------------------------------------------------------------------
All users are of course welcome to discuss their issues on the users mailing
list, where the developers also hang around.
+Please don't sent private support requests to individual Privoxy developers,
+either use the mailing lists or the support trackers.
+
Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
addresses have to be accepted manually by a moderator. This may cause a delay
of several days and if you use a subject that doesn't clearly mention Privoxy
projects / privoxy.git / blobdiff