Hi,
I would like to start releasing mod_jk 1.2.16 this week.
Since our last release was done from CVS and there are several updates
to the tool chain (autoconf/automake/m4/libtool), there is some risk of
breaking the release (additionally to mod_jk code bugs).
For that reason I would propose to tag as 1.2.16-rc1, because we might
need to have a second try on releasing it.
So I would propose, that I will
- take the role as RM for mod_jk 1.2.16
- tag mod_jk soon as 1.2.16-rc1
- roll a tarball and inform the dev- and user-list about availability of
a release candidate and invite to test it.
- in case of negative testing: fix, retag as rc2, reroll etc.
- after positive testing start the vote
- after positive voting copy the final rc-tag to 1.2.16 and reroll the
final release containing the right version numbers.
- finally announce the official release
Any comments?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
