What will it take for HornetQ to become ActiveMQ-6? That question keeps coming to mind.
At first, I was looking at the question strictly from a technical perspective. But considering the community and Apache involvement, the answer to that question becomes more complex. Naming releases of HornetQ at activemq-6.0.0-M1 presumes that HornetQ will succeed to replace ActiveMQ, and acts as a warning to all activemq users that the change is coming. But what if it does not succeed? Either on technical merits or on building community? The right path from the beginning has always been the incubator path. Let HornetQ prove itself as an Apache project and viable alternative to ActiveMQ without any attempt at using the ActiveMQ brand. Since HornetQ has been donated into ActiveMQ, we could certainly look to take some of the code from HornetQ and merge it into the existing ActiveMQ code base. No matter how we move forward, the issue of building community and HornetQ proving itself is the same. So, the question then becomes - what benefit is there to ActiveMQ and the ActiveMQ community? If we cannot enumerate a valid benefit for the community, then it does not belong there. -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693742.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
