Hello,
I'm thinking about branching JK, so adding
http://svn.apache.org/viewvc/tomcat/connectors/branches/jk1.2.x
and initially populate the branch with the contents of the 1.2.28 tag.
The motivation is to stabilize 1.2 and restrict further changes on 1.2
to patches only.
If we agree on such a plan, the more difficult discussion is about the
goals of the JK trunk. I basically see two options:
Option A) The big new thing
We collected ideas for a JK3 some years ago. Those included e.g.
migrating to APR and other big changes.
Option B) Proceed with relatively small changes and feature additions,
which are mostly locally. So then trunk would head for a 1.3 release.
I'm personally are in favour of option B. Not because of technical
reasons, but because of limited working time for the development task.
I'm very concerned, that if we decide for option A, we'll not be able to
proceed far enough for a stable release.
If we do option B: is it worth while? I think yes, there are still lots
of interesting and easy to implement features we can provide. For instance
- Saving changes done by the status worker
- Rotating log file for IIS
- Improving the status worker display
- Adding more connection parameters for dynamic management
- Adding more functionality to the watchdog thread (e.g. URL probing)
and much more.
Comments?
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
