On Thu, Jul 12, 2012 at 1:28 PM, Gordon Sim <[email protected]> wrote: > On 07/12/2012 06:14 PM, Rajith Attapattu wrote: >> >> I think we should also consider a separate JIRA instance to go with >> this > > > why?
I was thinking about having a single place to report all "AMQP" related issues. This includes proton, messenger API and the messaging API. IMO It makes sense to have the messaging API under the proton project as well. So perhaps something like "qpid-amqp" is a more appropriate name than qpid-proton . Good for google search too ;) Both 'amqp' and 'qpid' have brand value, so why not make use of it ? Apologies if I go off topic here, but thought it was somewhat relevant to this discussion. I think the following components could be thought of as sub projects and have independent release cycles. 1. AMQP libraries + client APIs 2. Messaging Brokers 3. Management tools (QMF and other tools) 4. JMS, WCF and other domain specific clients. Once we implement WCF and JMS properly I don't really see a point in releasing them with the brokers or the rest of the clients. Rajith > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
