<!entity p-intro SYSTEM "privoxy.sgml">
<!entity history SYSTEM "history.sgml">
<!entity seealso SYSTEM "seealso.sgml">
-<!entity p-version "3.0.25">
-<!entity p-status "UNRELEASED">
-<!entity % p-not-stable "INCLUDE">
-<!entity % p-stable "IGNORE">
+<!entity p-version "3.0.26">
+<!entity p-status "stable">
+<!entity % p-not-stable "IGNORE">
+<!entity % p-stable "INCLUDE">
<!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
<!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
<!entity % seealso-extra "INCLUDE"> <!-- extra stuff from seealso.sgml -->
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: developer-manual.sgml,v 2.68 2016/04/09 10:23:54 fabiankeil Exp $
+ $Id: developer-manual.sgml,v 2.75 2016/08/25 19:07:40 ler762 Exp $
Copyright (C) 2001-2016 Privoxy Developers https://www.privoxy.org/
See LICENSE.
</pubdate>
- <pubdate>$Id: developer-manual.sgml,v 2.68 2016/04/09 10:23:54 fabiankeil Exp $</pubdate>
+ <pubdate>$Id: developer-manual.sgml,v 2.75 2016/08/25 19:07:40 ler762 Exp $</pubdate>
<!--
<ulink url="https://www.privoxy.org/user-manual/contact.html">contact section in the user manual</ulink>
if you are interested in contacting the developers.
</para>
-<!-- <para> -->
-<!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
-<!-- </para> -->
</abstract>
</artheader>
<sect2 id="quickstart"><title>Quickstart to Privoxy Development</title>
<para>
The first step is to join the <ulink
- url="mailto:ijbswa-developers@lists.sourceforge.net">developer's mailing list</ulink>.
+ url="https://lists.privoxy.org/mailman/listinfo/privoxy-devel">privoxy-devel mailing list</ulink>.
You can submit your ideas, or even better patches. Patches are best
submitted to the Sourceforge tracker set up for this purpose, but
can be sent to the list for review too.
</listitem>
<listitem>
<para>
- If <filename>default.action</filename> has changed since last
- release (i.e. software release or standalone actions file release),
- bump up its version info to A.B in this line:
+ Update the code status (CODE_STATUS="xxx") to one of "alpha", "beta" or "stable".
</para>
+ </listitem>
+ <listitem>
<para>
+ If action file processing has changed and is not backward-compatable,
+ make sure the "for-privoxy-version=x.y.z" minimum version number in
+ default.action.master has been updated:
<programlisting>
- {+add-header{X-Actions-File-Version: A.B} -filter -no-popups}
+{{settings}}
+#############################################################################
+#MASTER# COMMENT: The minimum Privoxy version:
+for-privoxy-version=3.0.11
</programlisting>
</para>
- <para>
- Then change the version info in doc/webserver/actions/index.php,
- line: '$required_actions_file_version = "A.B";'
- </para>
</listitem>
<listitem>
<para>
For details see the <ulink url="https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/">FreeBSD Porter's Handbook</ulink>.
</para>
</sect3>
+ </sect2>
<sect2 id="releasing">
<title>Uploading and Releasing Your Package</title>
<title>After the Release</title>
<para>
When all (or: most of the) packages have been uploaded and made available,
- send an email to the <ulink url="mailto:ijbswa-announce@lists.sourceforge.net">announce
+ send an email to the <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">download