Now that's a good idea. Plus we need to get some headline issues in so we can build a JIRA "roadmap".
These spring to mind: 1) Complete local transaction support (XA not urgent at all) 2) High Availability for persistent message queues (*not* the same as clustering/federating for transient pubsub) 3) Staging for larger messages (will benefit from the work happening on the protocol content classes over at AMQP.ORG) 4) JMS Compliance (approximate first so people familiar with JMS don't get surprises; not aiming for TCK compliance of any sort on a first run, plus we don't have the TCK :-) 5) Performance Correct first, then fast :-) Anyone else got a pressing view? John On 06/10/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
I'd like to request that as a way of getting more community involved with Qpid, those of you who have worked on this codebase for awhile populate JIRA with issues that you know need to be fixed or addressed. It's hard to come into the codebase cold and figure out where to meaningfully put effort, but if there are items in JIRA, then potential contributors can browse through and easily find stuff to work on. --steve
