On 1/18/06, Jesper B. Kiær <[EMAIL PROTECTED]> wrote: > What are the > > - visions for project? > - roadmaps > - plans > - ...
That's all in the wiki. The near-term changes are in JIRA's release notes (our issue tracker), and of course mailing list archives if you want to search a bit. IMO James is reasonably documented compared to most open source projects, largely because it's stabilized and hasn't had radical changes. We do not have as much active development as other projects, but the developer list has sustained traffic even if at low volume. Please also note that these are surrogate indicators of a project's quality. James is a very excellent replacement for sendmail. I would never consider it a replacement for Exchange, but it does what it tries to do very well. Sendmail has much more documentation and developer traffic, but I have yet to figure out how to edit and compile the sendmail configuration files to manage what I consider basic smtp gateway functionality. Maybe it's our name that causes us problems. When we say "Enterprise Mail Server" we mean enterprise messaging like routing and logging and transforming and processing. I think unfortunately for us, a large number of people hear "Enterprise Mail Server" and they think we should be able to handle imap and calendar and contacts for 20-100 people (Exchange). We do not do that (at least not until someone contributes that). -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
