I don't see how a separate hornetQ project is a clear declaration of ActiveMQ's future, nor why that matters to the discussion.
Wanting to engage the existing ActiveMQ community to the benefit of HornetQ is understandable, but that doesn't make it the right thing to do. Especially for ActiveMQ and its community. On the topic of starting a new broker project - do we need a *new* broker project? What problems are we solving? And for whom are we solving them? By the way - we already have a "many-dev-years of code advanced broker". It's called ActiveMQ, and it is very popular. And, back to the core question at hand. What benefit does the ActiveMQ community obtain from this path? Any attempt to move HornetQ forward as ActiveMQ-6.0.0-M1 without addressing that question is lacking merit. Oh, and for the record - I personally am interested in HornetQ and may contribute to the project wherever it lives, so the question-at-hand isn't whether we are helping to move HornetQ forward. -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693747.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
