Stefano Bagnara schrieb:
Hi all,
From the last status-update from Joachim, I understand that he's very
near to have something working and that does not need changes on our
main codebase.
Now that Joachim is a James Committer and has write access to SVN
(Joachim: can you check your svn account works?) we have to decide
what to do.
I think we should ask him to commit his work in server/sandbox/imap so
we can review it and eventually merge it to trunk.
Same here..
Imho we can let him skip the packaging and the documentation he did in
past to post his work on JIRA, because he will do the work needed to
integrate (very small work) it in trunk and then it will be much more
easy for users that want to try IMAP as we'll bundle it in the default
distribution.
I also think that it should be safe for us to include the code in the
next-release: we'll decide wether to make it "public" (publicize it)
or not in function of the stability and the architecture it will have
when we'll make the next release (like we did for fastfail).
I expect that it will be included but disabled by default and marked
as experimental in the next release due for 1st quarter 2007.
I think thats realistic. At least i hope so..
Do we need Joachim to sign a Software Grant
(http://www.apache.org/licenses/software-grant.txt) for this?
If he not publish it yet as official release we not need this.. correct
me if im wrong..
Further inline comments follows:
Joachim Draeger wrote:
A quick status of http://issues.apache.org/jira/browse/JAMES-502:
Because discussion of my API proposal published as
repository-proposal-3.zip at JIRA and on my website
http://www.joachim-draeger.de/JamesImap/
hibernated, I decided to start a prototype implementation which uses
JDBC/Torque with MySQL or Derby, under the working title MailboxManager.
Then I refactored the IMAP code to use the new API.
Everything works quite well at the moment. I have unit tests for all
basic operations.
I know that past unit tests where tightly linked to maildir: I also
saw that you made steps since that time and now it seem you separated
generic tests from maildir tests from mstor tests.
We can't incldue javamaildir stuff in our repository: does including
all of the remaining things make sense? Is this already working?
I just did the integration with current James trunk.
I did it completely without changing current James code. Just putting,
some jars into SAR-INF/lib and modifying assembly.xml.
I soon publish it at JIRA, when I find the time to do the packaging with
some documentation. (It always costs a lot of time so if you want to
be up-to-date look at my svn)
As this is clearly a cost (time) I think we should skip this and you
should itegrate it into the main codebase in the sandbox so we see
what are the needed changes in svn notifications (international
language :-) )
Once it will be integrated we'll need less documentation for
users/developers to start working on it.
+1
For the impatient: http://svn.joachim-draeger.de/repos/james/imap/
http://svn.joachim-draeger.de/repos/james/mailboxmanager/
My ideas to the roadmap topic:
- after publishing API with prototype running together with imap in
James I hope for some review.
- maybe we are able to make some decisions then
- we have to decide if/how to integrate the code - for integration
everything (sandbox/branch/product/trunk) is imaginable, because it
does not interfere with existing code.
Joachim
I don't know if this roadmap is intended as a sorted list: in this
case I would change the order because I think that integration should
be the first task.
I think that we should use an agile approach to this task:
- commit it to sandbox (branch trunk, add your components, make
configuration changes)
- "official" review/test from us
- when any "blocker" issue is solved merge it to trunk
- then I expect we can discuss and refactor it while a working version
is in trunk: maybe someone will start short-living branches to show
his ideas.
WDYT?
Stefano
PS: I reviewed Joachim's code few weeks ago, and there are few choices
that I didn't like at first. But I think that blocking it with endless
discussions will never bring us IMAP, so I'll wait to see the code
working and integrated in trunk and I'll try to make my proposals
about refactorings/api changes later.
I agree with Stefano. Joachim should commit his work in sandbox. Then we
should test and "fix" problems. After all is workin we should merge it
bye
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
