X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=README;h=d09bb0bc43764b639371741a396972306f9f12f1;hb=63406a6676b846d4c17b506fb3dd8f053425ce6f;hp=881a25f29199ce6303f09ef2c837a45feefe5214;hpb=5a9fe9bb1c92df42990e31151f8138d008357b9d;p=privoxy.git

diff --git a/README b/README
index 881a25f2..d09bb0bc 100644
--- a/README
+++ b/README
@@ -4,7 +4,7 @@
  *
  * Purpose     :  README file to give a short intro.
  *
- * Copyright   :  Written by and Copyright (C) 2001-2008  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
@@ -32,7 +32,7 @@
  *
  *********************************************************************/
 
-This README is included with the development version of Privoxy 3.0.9. 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 "UNRELEASED", but seems stable to us :).
 
@@ -51,30 +51,25 @@ Privoxy is based on Internet Junkbuster (tm).
 
 1. IMPORTANT CHANGES
 
-Privoxy is in development mode for the time being. Some of the current cvs
-sources may not be well tested, and/or well documented. Current cvs is
-suggested only for developers and adventuresome users. If you find any
-problems, please report them on the appropriate SourceForge tracker, or the
-developer's mailing list: ijbswa-developers@lists.sourceforge.net. Your help
-will be appreciated!
+Privoxy is between releases. The current code base should be considered
+development quality. Please report any problems to the developers.
 
-NEWS! January 2008, Privoxy 3.0.8 stable is released. This is a significant
-upgrade with many new and enhanced features, and many bugs fixed. All Privoxy
-users are encouraged to upgrade. 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.
+February 2009, Privoxy 3.0.11 is released.
 
-December 2007, Privoxy 3.0.7 is released. This is a beta release in preparation
-for the forthcoming 3.0.8 release.
+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.
 
-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.
 
 -------------------------------------------------------------------------------
 
@@ -99,7 +94,7 @@ file named 'config' in the current directory (except Win32 which will look for
 
 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
 
 -------------------------------------------------------------------------------
 
@@ -162,6 +157,9 @@ http://sourceforge.net/tracker/?group_id=11118&atid=211118
 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