We might want to record our collective ideas on the wiki, where we already have others: http://wiki.apache.org/james/JamesV3. Looks like we've already done some, and have new ideas on others. Serge would probably suggest, and he's right, that we start to use JIRA to layout our roadmap concretely.
I may/may not suggest this, and am not sure whether I'm right. ;)
What's in the wiki is a list of goals, while JIRA is nice for discrete tasks. I would prefer to use JIRA to track each developer/code change, e.g., "JNDI support" may be 1 issue, it might be 6, so having the wiki set the goal of JNDI is fine.
I'm also just looking for JIRA to helping with changelogs and track bugs. I don't know any tool that really helps with release or product planning.
</ramble>
-- 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]
