i've been having a little think recently, in particular about user
postings on the list. i think i can see a realistic path if there's a
consensus that this is the way we want to take james forward...
Observations:
* Felix Karaf (OSGi container) is very cool. this opens up lots of
cool possibilities for mixing protocols and is very interesting to me.
* IMAP may well be ready for a 0.1 release in the near future :-) but
will focus on spring and OSGi tooling with only limited support for
avalon
* Stefano and Norman are very busy these days. so just directly
releasing 3.0 is looking harder and harder...
* The recent threads from users are telling us that we really need to
have a 2.x roadmap for mail server users (as opposed to mail
application developers)
Proposal:
* Use 2.x for mature, stable releases aimed at mail server users
retaining pheonix as the container
* Target 3.x at mail application developers focussing on OSGi and Spring
* Move code from 3.x to 2.x by factoring out libraries with multiple
modules to allow optional avalon and OSGi service support
Roadmap:
* Release 2.3.2 now (after deprecating mordered, crypto)
* Release standard mailets 1.0
* Release crypto mailets 1.1 targeting java 1.5
* Release 2.4 soon replacing source with jars released so far (with
note about standard mailets)
* Compiled against Java 1.5
* Remove mordred
* Replace 2.x crypto source with released jar
* Replace 2.x mailet API with released jars
* Release 2.5 later replacing source with released jars
* Add jSPF support
* Replace standard mailet source with released jar
* Replace whichever other services have been released by then
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
