Hi all!
Still lurking around here and following the mailing lists. I'm pleased to see
how the James 2.3.0 release makes such great progress, although JAMES-603 looks
really ugly.
I've postponed development on the IMAP code until there is a suitable repository
API for James.
Because this is affecting whole James I really can't do that on my own. I
started writing drafts and interfaces to collect the requirements.
But I got the feedback that everyone wanted to concentrate on the 2.3.0 release
at that time.
Now, as the release date comes nearer and people starting discussion for new
features and roadmap again, I suggest working on the repository API before going
back to routine and start working on 2.4.0.
Greetings,
Joachim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
