activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hiram Chirino <>
Subject Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)
Date Fri, 20 Mar 2015 20:14:29 GMT
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

On Friday, March 20, 2015, artnaseef <> 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:
> 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:
> Sent from the ActiveMQ - Dev mailing list archive at

Hiram Chirino
Engineering | Red Hat, Inc. | |
skype: hiramchirino | twitter: @hiramchirino

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message