I don't disagree. Create jiras and for those issues in JIRA. We can then figure out ways to mitigate them to make the transition easier for AMQ 5 users.
On Friday, March 20, 2015, artnaseef <[email protected]> wrote: > +1 > > A complete rewrite means users need to carefully look at what's there and > what's not, and those of us building the software need to put in extra > effort to even figure that out ourselves. It also means starting over on > learning the software (how to install, configure, deploy, operate, monitor, > alert, etc). > > A major version bump on projects may involve refactoring and reworking > significant parts of the code, and when it does, it's clear to the > developers what has been changed and lost from the prior release. Then > it's > easy to document. (Like this: http://tomcat.apache.org/migration-8.html). > > If we had a list of all ActiveMQ features, and the state of those features > in HornetQ (e.g. implemented, partially implemented, won't implement, etc), > that would certainly go a long way to furthering the entire discussion. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693553.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > -- Hiram Chirino Engineering | Red Hat, Inc. [email protected] | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
