<para>
Note that near a major public release, we get more cautious.
There is always the possibility to submit a patch to the <ulink
- url="https://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse">patch
+ url="https://sourceforge.net/p/ijbswa/patches/">patch
tracker</ulink> instead.
</para>
</listitem>
Alternately, proposed changes can be submitted as patches output by
<literal>git format-patch</literal> to the privoxy-devel mailing list
or alternatively to the patch tracker on Sourceforge:
- <ulink url="https://sourceforge.net/tracker/?group_id=11118&atid=311118">
- https://sourceforge.net/tracker/?group_id=11118&atid=311118</ulink>.
+ <ulink url="https://sourceforge.net/p/ijbswa/patches/">
+ https://sourceforge.net/p/ijbswa/patches/</ulink>.
Then ask for peer review.
</para>
</listitem>
be reset to one if this is the first RPM for
<replaceable class="parameter">dist</replaceable> which is built from version
X.Y.Z. Check the
- <ulink url="https://sourceforge.net/project/showfiles.php?group_id=11118">file
+ <ulink url="https://sourceforge.net/projects/ijbswa/files/">file
list</ulink> if unsure. Else, it must be set to the highest already available RPM
release number for that version plus one.
</para>
<ulink url="mailto:privoxy-announce@lists.privoxy.org">announce mailing
list</ulink>, Subject: "Version X.Y.Z available for download". Be sure to
include the
- <ulink url="https://sourceforge.net/project/showfiles.php?group_id=11118">
+ <ulink url="https://sourceforge.net/projects/ijbswa/files/">
download location</ulink>, the release notes and the Changelog. Also, post an
updated News item on the project page Sourceforge, and update the Home
page and docs linked from the Home page (see below). Other news sites