current/doc/text developer-manual.txt, 1.39, 1.40 faq.txt, 1.52, 1.53 user-manual.txt, 1.69, 1.70

Update of /cvsroot/ijbswa/current/doc/text
In directory sc8-pr-cvs2.sourceforge.net:/tmp/cvs-serv24968/doc/text

Modified Files:
        developer-manual.txt faq.txt user-manual.txt 
Log Message:
Updated for 3.0.7 beta


Index: developer-manual.txt
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/text/developer-manual.txt,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- developer-manual.txt        7 Dec 2007 11:57:45 -0000       1.39
+++ developer-manual.txt        8 Dec 2007 14:40:10 -0000       1.40
@@ -1479,8 +1479,8 @@
  *
  * Revisions   :
  *    $Log$
- *    Revision 1.39  2007/12/07 11:57:45  hal9
- *    For stable release.
+ *    Revision 1.40  2007/12/08 14:40:10  hal9
+ *    Updated for 3.0.7 beta
  *
  *
  *********************************************************************/
@@ -1541,8 +1541,8 @@
  *
  * Revisions   :
  *    $Log$
- *    Revision 1.39  2007/12/07 11:57:45  hal9
- *    For stable release.
+ *    Revision 1.40  2007/12/08 14:40:10  hal9
+ *    Updated for 3.0.7 beta
  *
  *
  *********************************************************************/
@@ -2049,7 +2049,7 @@
 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:
 
-  debchange -v 3.0.7-stable-1 "New upstream version"
+  debchange -v 3.0.7-beta-1 "New upstream version"
 
 
 Then, run:
@@ -2057,7 +2057,7 @@
   dpkg-buildpackage -rfakeroot -us -uc -b
 
 
-This will create ../privoxy_3.0.7-stable-1_i386.deb which can be uploaded. To
+This will create ../privoxy_3.0.7-beta-1_i386.deb which can be uploaded. To
 upload the package to Sourceforge, simply issue
 
   make debian-upload


Index: user-manual.txt
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/text/user-manual.txt,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- user-manual.txt     7 Dec 2007 11:57:45 -0000       1.69
+++ user-manual.txt     8 Dec 2007 14:40:12 -0000       1.70
@@ -212,16 +212,24 @@
 
 1. Introduction
 
-This documentation is included with the current stable version of Privoxy,
-v.3.0.7.
+This documentation is included with the current beta version of Privoxy,
+v.3.0.7, and is mostly complete at this point. The most up to date reference
+for the time being is still the comments in the source files and in the
+individual configuration files. Development of a new version is currently
+nearing completion, and includes significant changes and enhancements over
+earlier versions. .
+
+Since this is a beta version, not all new features are well tested. This
+documentation may be slightly out of sync as a result (especially with CVS
+sources). And there may be bugs, though hopefully not many!
 
 
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??
 
 1.1. Features
 
 In addition to the core features of ad blocking and cookie management, Privoxy
-provides many supplemental features, that give the end-user more control, more
-privacy and more freedom:
+provides many supplemental features, some of them currently under development,
+that give the end-user more control, more privacy and more freedom:
 
   â?¢ Integrated browser based configuration and control utility at http://
     config.privoxy.org/ (shortcut: http://p.p/). Browser-based tracing of rule
@@ -427,8 +435,8 @@
 
 When building from a source tarball, first unpack the source:
 
- tar xzvf privoxy-3.0.7-src* [.tgz or .tar.gz]
- cd privoxy-3.0.7
+ tar xzvf privoxy-3.0.7-beta-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.7-beta
 
 
 For retrieving the current CVS sources, you'll need a CVS client installed.
@@ -1144,7 +1152,9 @@
 
 For Unix, *BSD and Linux, all configuration files are located in /etc/privoxy/
 by default. For MS Windows, OS/2, and AmigaOS these are all in the same
-directory as the Privoxy executable.
+directory as the Privoxy executable. The name and number of configuration files
+has changed from previous versions, and is subject to change as development
+progresses.
 
 The installed defaults provide a reasonable starting point, though some
 settings may be aggressive by some standards. For the time being, the principle
@@ -1200,6 +1210,11 @@
 effect. When changing the listening address of Privoxy, these "wake up"
 requests must obviously be sent to the old listening address.
 
+While under development, the configuration content is subject to change. The
+below documentation may not be accurate by the time you read this. Also, what
+constitutes a "default" setting, may change, so please check all your
+configuration files on important issues.
+
 
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??
 
 7. The Main Configuration File


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php_______________________________________________
ijbswa-commits mailing list
ijbswa-commits@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ijbswa-commits