We should have a plan and release manager for the next major release. Here are some ideas. - Have a single, standard repository API. Noel, others have mentioned JNDI. - Move all protocols including NNTP to use that repository API. - IMAP Server support. - Test Bed to check RFC compliance, performance and stability. - Experimental MS Exchange Protocol Support. - Move away from Avalon/Phoenix. There has been some talk on this topic. We could keep the framework part and not use Phoenix if this is a sensible goal.
I think, we should first only collect all the possible things we could do and then figure out what it takes to do it i.e. design changes etc. It may also be a good idea to cap the expected time frame of next release. A good time frame may be 6-9 months. comments... Harmeet -- To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
