Harmeet Bedi wrote:
We should have a plan and release manager for the next major release.
+1
I would rehprase the last point - istead of moving away from Phoenix, think about it as seperating execution from deployment cocerns. Phoneix is a cool application for handling complex component deployment. The key feature of seperation is being able to choose - and choice is liberty.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.
Cheers, Steve.
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>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
