Rebuild HTML docs

[privoxy.git] / doc / webserver / developer-manual / newrelease.html

diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html
index a5dc71a..04edd94 100644 (file)
--- a/doc/webserver/developer-manual/newrelease.html
+++ b/doc/webserver/developer-manual/newrelease.html
@@ -618,7 +618,7 @@ for-privoxy-version=3.0.11</pre>
           <tr>
             <td>
               <pre class="PROGRAMLISTING">
-              debchange -v 3.0.26-stable-1 "New upstream version"</pre>
+              debchange -v 3.0.27-UNRELEASED-1 "New upstream version"</pre>
             </td>
           </tr>
         </table>
@@ -632,7 +632,7 @@ for-privoxy-version=3.0.11</pre>
           </tr>
         </table>
         <p>This will create <tt class=
-        "FILENAME">../privoxy_3.0.26-stable-1_i386.deb</tt> which can be
+        "FILENAME">../privoxy_3.0.27-UNRELEASED-1_i386.deb</tt> which can be
         uploaded. To upload the package to Sourceforge, simply issue</p>
         <table border="0" bgcolor="#E0E0E0" width="100%">
           <tr>
@@ -786,7 +786,7 @@ for-privoxy-version=3.0.11</pre>
       column, and click <tt class="LITERAL">Add Release</tt>. You will then
       need to create a new release for your package, using the format of
       <tt class="LITERAL">$VERSION ($CODE_STATUS)</tt>, e.g. <span class=
-      "emphasis"><i class="EMPHASIS">3.0.26 (beta)</i></span>.</p>
+      "emphasis"><i class="EMPHASIS">3.0.27 (beta)</i></span>.</p>
       <p>Now just follow the prompts. Be sure to add any appropriate Release
       notes. You should see your freshly uploaded packages in <span class=
       "QUOTE">"Step 2. Add Files To This Release"</span>. Check the