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

Lee ler762 at gmail.com
Sun Jul 15 03:53:53 UTC 2018


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?

Lee


More information about the Privoxy-devel mailing list