current/doc/source developer-manual.sgml, 2.80, 2.81

Update of /cvsroot/ijbswa/current/doc/source
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv30790/doc/source

Modified Files:
	developer-manual.sgml 
Log Message:
Shorten update instructions

The dok-release target takes care of the SGML entity updates.


Index: developer-manual.sgml
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/source/developer-manual.sgml,v
retrieving revision 2.80
retrieving revision 2.81
diff -C2 -d -r2.80 -r2.81
*** developer-manual.sgml	26 Aug 2016 12:32:07 -0000	2.80
--- developer-manual.sgml	26 Aug 2016 12:32:19 -0000	2.81
***************
*** 2103,2113 ****
         <para>
           Increment the version number (point from odd to even in development
!          branches!) in <filename>configure.in</filename>. (RPM spec files
!          will need to be incremented as well.)
         </para>
        </listitem>
        <listitem>
         <para>
!          Update the code status (CODE_STATUS="xxx") in <filename>configure.in</filename> to one of "alpha", "beta" or "stable".
         </para>
        </listitem>
--- 2103,2115 ----
         <para>
           Increment the version number (point from odd to even in development
!          branches!) in <filename>configure.in</filename> and update the code
!          status (CODE_STATUS="xxx") to one of "alpha", "beta" or "stable".
!          Rebuild configure and GNUMakefile to make sure the updated values are
!          being used.
         </para>
        </listitem>
        <listitem>
         <para>
!         Use the dok-release target to update the sgml documentation source files.
         </para>
        </listitem>
***************
*** 2127,2155 ****
        <listitem>
         <para>
-         Update the sgml documentation source files with the version number
-         <programlisting>
- &lt;!entity p-version "3.0.26"&gt;
- </programlisting>
-         and set the code status
-         <programlisting>
- &lt;!entity p-status "stable"&gt;
- </programlisting>
-         to one of "alpha", "beta" or "stable" in
-         <programlisting>
-   current/doc/source/authors.sgml
-   current/doc/source/config.sgml
-   current/doc/source/developer-manual.sgml
-   current/doc/source/faq.sgml
-   current/doc/source/install.sgml
-   current/doc/source/privoxy-man-page.sgml
-   current/doc/source/readme.sgml
-   current/doc/source/user-manual.sgml
- and in
-   current/doc/source/webserver/index.sgml
- </programlisting>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
          All documentation should be rebuild after the version bump.
          Finished docs should be then be committed to CVS (for those
--- 2129,2132 ----


------------------------------------------------------------------------------