Costin Manolache wrote:
I was thinking more as
- when all the new features are implemented and we have a replacement
protocol that has been
around ( optional ) for a while - drop the old code and branch 1.3.
This is certainly one approach, but from my humble
experience that won't do any good.
Putting new wine into old wineskins will just break
both things.
We wanna make sure 1.2 branch is stable, but still
address new emerging technology concepts that simply
cannot be solved with current design.
The first approach gives a swift jump start for sure,
but at the end, the workable solution almost certainly
takes more time to develop then something designed
correctly from the ground up.
Regards
--
^(TM)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
