[Privoxy-devel] doc-dev: Before/After the release

[Fabian Keil]

Lee <ler762 at gmail.com> wrote:

> The release process doesn't seem to match the documentation.  This
> seems to be closer to what actually happens:
> 
> in section
> 6.5. After the Release
> 
> add new bullet points for
> 
> - increment the version number and change the code status to
> "UNRELEASED" in configure.in
> 
> - Rebuild configure (autoheader && autoconf) and GNUMakefile (./configure)
> 
> - 'make dok-release' to update the sgml documentation source files
> 
> 
> and then for
> 6.2. Before the Release
> 
> the bullet point for
> - Increment the version number (point from odd to even in development
> branches!) in configure.in 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.
> 
> becomes
> - Update CODE_STATUS in configure.in to one of "alpha", "beta" or "stable".
> 
> - Rebuild configure (autoheader && autoconf) and GNUMakefile
> (./configure)  to make sure the updated values are being used.
> 
> - 'make dok-release' to update the sgml documentation source files.
> 
> 
> thoughts?

Makes sense. Please go ahead and do it.

Fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20180718/3b0d3b3e/attachment.bin>