On Thu, 24 Mar 2005 09:37:32 -0800 "Claude Duguay" <[EMAIL PROTECTED]> wrote:
1) I was dissapointed to see that, while a fix that was provided, ready-made, a bug that seemend important to me was still in UNRESOLVED status. Unfortunately, I took it for granted that a ready-made fix would not remain UNRESOLVED for long and upgraded to James 2.2.0 on my production server, only to find that the RemoteDelivery gateway configuraiton does not allow for defining a username and password for authentication. My questions related to this are: a) Why has the fix not been incorporated? b) When will it be?
There are no simple answers. We have lack of active developers. You can blame that on sick of working on the old Avalon platform, growing families, contracting picking up, SVN migration, etc... But bottom line is no committers are actively developing James. Your issue in JIRA is right where it should be, and I'm sure that's the best way to get it reviewed and incorporated. There are several other patches that are sitting in JIRA waiting to be added as well, so it has nothing to do with your patch AFAIK.
2) I'm finidng the long wait for IMAP support highly questionable. Though I'm glad to see that there is discussion of classloader-separated mailet packages, it's dissapointing that this is also not present in the current release. The two articles about James that I published for IBM were released in June of 2003, close to two years ago. I can't conceive of any reason why both the classloader deployment and IMAP support have been so long in comming. I'm not really asking why. What I'd really like to hear is a commitment to get the job done and a timeline to covers these two critical features, still not in place despite a clear understanding that they are important to the user community. It's a tough sell when there's no IMAP support and 'they're working on it' isn't really cutting it anymore. Comments?
I don't tell people that we're working on IMAP... it's an experimental feature without any active development. There are a few people who have worked at it, but unfortunately there has not been enough free time to get it ready for prime time. It is a big limitation of IMAP, but unfortunately in a project like this, the squeeky wheel doesn't get the grease so much as the personal itch gets scratched (sorry for my euphemisms).
We are actively supporting as many users as possible through the mailing lists, and otherwise sustaining the project... think of it as development hibernation, not termination. I'm aware that myself, Noel, Danny, and Vicenzo are working intermittently on James but have not had time to take the lead or substantively do any development.
I feel like I've written this type of email a few too many times, sounding half defeatist/half hopeful. Still, I'd rather answer your email than let something like that go unanswered.
-- Serge Knystautas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
