Generated

[privoxy.git] / doc / text / developer-manual.txt

diff --git a/doc/text/developer-manual.txt b/doc/text/developer-manual.txt
index 59ba048..b5377eb 100644 (file)
--- a/doc/text/developer-manual.txt
+++ b/doc/text/developer-manual.txt
@@ -411,7 +411,7 @@ entities are listed below. See any of the main docs for examples.
    
   * Commonly used "internal entities":
    
-    p-version: the Privoxy version string, e.g. "2.9.16".                      
+    p-version: the Privoxy version string, e.g. "2.9.18".                      
     p-status: the project status, either "alpha", "beta", or "stable".         
     p-not-stable: use to conditionally include text in "not stable" releases   
     (e.g. "beta").                                                             
@@ -1798,13 +1798,13 @@ First, 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:
 
-  debchange -v 2.9.16-beta-1 "New upstream version"                            
+  debchange -v 2.9.18-beta-1 "New upstream version"                            
 
 Then, run:
 
   dpkg-buildpackage -rfakeroot -us -uc -b                                      
 
-This will create ../privoxy_2.9.16-beta-1_i386.deb which can be uploaded. To
+This will create ../privoxy_2.9.18-beta-1_i386.deb which can be uploaded. To
 upload the package to Sourceforge, simply issue
 
   make debian-upload                                                           
@@ -1925,7 +1925,7 @@ Once this done go to http://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 Release. You will then need to create a new
 release for your package, using the format of $VERSION ($CODE_STATUS), e.g.
-2.9.16 (beta).
+2.9.18 (beta).
 
 Now just follow the prompts. Be sure to add any appropriate Release notes. You
 should see your freshly uploaded packages in "Step 2. Add Files To This
@@ -2097,8 +2097,8 @@ Then, some developers picked up the thread, and started turning the software
 inside out, upside down, and then reassembled it, adding many new features
 along the way.
 
-The result of this is Privoxy, whose first stable release, 3.0, is due in June
-2002.
+The result of this is Privoxy, whose first stable release, 3.0, is due late
+summer or early fall 2002.
 -------------------------------------------------------------------------------
 
 10. See also