tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rees" <>
Subject Re: mod_jk release plan
Date Tue, 27 Jun 2006 20:49:52 GMT
On 6/27/06, Rainer Jung <> wrote:
> - 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.

Why not do releases like tomcat/httpd do it? Go ahead and
rollup/release 1.2.16, then vote on the stability. If there are
problems, roll up another release (1.2.17) for more testing. Repeat
until you have a tarball that is ready for production, that way you
still don't risk the chance of breaking something when you re-tag the
non-rc release and rebuild the tarball (however small that chance may
be) because if you do, you'll have to bump the version number and
re-release anyway.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message