Slightly more than a month ago I wrote a roadmap, here is an update for people that has not time for a day to day oversight.

Stefano Bagnara wrote:
Norman Maurer wrote:
I agree with Stefano.. And i think we can push a 2.4 release in 6 Month
( At least i hope so).
So i think the next step must a roadmap! First we should dedicide which
jira issues should be moved to 2.4 before do anything else. Without a
roadmap we only make it more complicated.

My proposal is:
- everything we have in trunk now: now I can't see anything critical
enough to be removed.

Well, this was already there ;-)

- JAMES-426 - Make james use virtual user table domains for servernames

This is done.

- JAMES-52 - 8bitmime capabilities missing

It seems that javamail 1.4.1ea fixed the problem and we reenabled the support for it!

- JAMES-487 - Refactor Bundled handlers to use the "HandlerChain" pattern

This is blocked by the handlerapi work in sandbox.

- JAMES-577 - Switch default sendpartial to true for RemoteDelivery

Done.

- JAMES-607 - Rewrite MBoxMailRepository to use mstor

We wrote the support for this: Joachim found 3 blocking bugs in mstor. 2 of them have been fixed, so as soon as mstor will fix the third and make a release this will be fixed.

- JAMES-611 - Remove finalizers and make sure we always call dispose
when unreferencing objects

Done.

- JAMES-461 - Javamail Store based MailRepository support (was: Maildir
support)

Joachim contributed this. Applied.

- JAMES-614 - Add more actions to FastFailHandlers

In progress: Norman is working on this.

- JAMES-549 - Refactoring SMTPHandler to allow better integration of
more the one class per command

Blocked by the new handlerapi in sandbox.

- JAMES-599 - BeanShell Scripting in James

Code has been provided by Guillermo.
We should probably vote to decide wethere to include this or not.
I wrote a message in past to understand wether there was preference for this BeanShell solution or on the BSF mailet: I would like to see the BSF mailet code before deciding, but I can't find it.

- JAMES-562 - Aliasmanagment should not depend on a user (see as
VUT-UsersAliasingForwarding common interface and remove tightly
dependencies between James and JamesUser)

Almost done.

- JAMES-595 - Change names of release artifacts to use james-server
instead of james.

Open (but easy to do).


That said, currenlty blocking issues are:

1) dnsjava 2.0.3 release (to support JSPF)
   (we are currenlty including a snapshot of dnsjava trunk)

2) javamail 1.4.1 release (8bitmime bugs)
   (we are currenlty including 1.4.1ea-SNAPSHOT from their m2 repository)

3) mstor release (to replace internal mbox management with mstor)
(2 of 3 bugs have been fixed in cvs, so we should be able soon to include a working snapshot or the fixed release)

4) handlerapi v2.
   (If I understood it right, Noel is almost ready with his work)


I think that if we can comlpete the handlerapi stuff soon we could realistically consider branching for a release at the start of december (almost a month before what was in the plans)

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to