Finished docs should be then be committed to CVS (for those without
the ability to build these). Some docs may require rather obscure
processing tools. <tt class="FILENAME">config</tt>, the man page
- (and the html version of the man page), and the PDF docs fall in
- this category. REAMDE, the man page, AUTHORS, and config should all
- also be committed to CVS for other packagers. The formal docs
- should be uploaded to the webserver. See the Section "Updating the
- webserver" in this manual for details.</p>
+ (and the html version of the man page) fall in this category.
+ REAMDE, the man page, AUTHORS, and config should all also be
+ committed to CVS for other packagers. The formal docs should be
+ uploaded to the webserver. See the Section "Updating the webserver"
+ in this manual for details.</p>
</li>
<li>
<tr>
<td>
<pre class="PROGRAMLISTING">
- debchange -v 3.0.21-UNRELEASED-1 "New upstream version"
+ debchange -v 3.0.24-stable-1 "New upstream version"
</pre>
</td>
</tr>
</table>
<p>This will create <tt class=
- "FILENAME">../privoxy_3.0.21-UNRELEASED-1_i386.deb</tt> which can be
+ "FILENAME">../privoxy_3.0.24-stable-1_i386.deb</tt> which can be
uploaded. To upload the package to Sourceforge, simply issue</p>
<table border="0" bgcolor="#E0E0E0" width="100%">
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.21 (beta)</i></span>.</p>
+ "emphasis"><i class="EMPHASIS">3.0.24 (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=