Hi Art, Thanks for trying to bring me back to earth :-)
I think I understand a bit more of what you are concerned about, and your concerns are definitely worth discussing, although I think in some of your earlier posts we disagree a lot on what is going on. - name: I don't think anyone cares any more that formerly-hornetQ be called activemq-6 right now. I hope this would alleviate your concern that it will necessarily be the next activemq even if it doesn't work :-) - need for new broker: Other people have explained way better than I can why a new broker might greatly broaden where activemq could be used. I don't want to see activemq disadvantaged on say relatively slow processors with a lot of cores. - concern about backwards compatibility and getting into a no-migration bind. This is a big problem, and a big danger, and Raj seems to be saying it could take years to make it completely backwards compatible (hopefully not replicating bugs :-) However, if I understood his post correctly, activemq has already had 4 broker replacements and it's still going strong. So I don't see this as an insuperable obstacle. You've also said some things that don't match up with what it looks to me like is going on. I'm pretty sure you are more involved than I, so you might have more evidence, but I haven't seen it. - hornetQ is replacing activemq, rather than merging code into the existing activemq code base. I've tried to address this repeatedly. The only way I can imagine the integration working, since everything is attached to the broker, is to start with the new broker and add everything that isn't the broker to it, changing both as needed so it works. As far as I can tell this is exactly what is happening. What other plausible merge/integration strategy can you imagine? At the beginning of this process the new code repository is going to look like former-hornetq with the name changed. As bits get added it's going to look more and more like activemq 5 does now. - hornetQ is going to continue to exist as a separate messaging solution and entity. My understanding has always been 100% that the hornetQ intent is to merge the code bases, drop the hornetQ name, and not have any separate hornetQ code base, community, project, product….. Finally, I don't see what the board can offer for these questions, I think the community has to decide what it wants to do. There' might well be community problems and I'd expect the board to address those. Unless I'm wrong about the last point, hornetQ continuing as a separate project, I don't see any of these as community problems but rather technical decisions about the project direction. I sure hope we can continue with more communication and less noise :-) And I hope I haven't missed any concerns you regard as important. thanks david jencks On Mar 28, 2015, at 2:24 PM, artnaseef <a...@artnaseef.com> wrote: > David - please go back and read my posts (user name artnaseef, full name > Arthur Naseef). I have repeated myself multiple times with concerns. And > there has not been constructive response to my concerns, nor to questions I > posed in an attempt to get clarity on the position that ActiveMQ needs a new > broker. > > It is disappointing because I know there is valid discussion there. > > I agree this thread contains much passion and input that is unactionable > (i.e. pure criticism), and that sucks because it will never serve to move > use forward, reach conclusion, nor build consensus. At the same time, it's > understandable and I recognize that I have inserted some myself. So let me > be the first to apologize. I'm sorry for statements that I've made which > have not been constructive. > > Getting back to the actionable concerns raised and finding a way to address > them going forward would be greatly appreciated. > > If you want me to rehash my concerns, then I'll do so, but I would prefer to > avoid repeating myself multiple times. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4694024.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
