Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of raul@evosent.com designates
 209.85.192.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4DA484E1-40FD-4D61-87C4-0F8E511B047F@gmail.com>
References: <55127628.2030008@gmail.com>
	<CAH+vQmMZhnLJNRc4Y761RTv9OZxc6+drVRM-EEeKRR3xYTEOUw@mail.gmail.com>
	<1427299537888-4693805.post@n4.nabble.com>
	<14F45FF3-17F1-4CCF-8276-ABABC1AD57E4@yahoo.com>
	<5512FDEF.7030608@gmail.com>
	<CAA9ykMJj4Gk+6tQLQbaPhS_z+O55ubo9yLAv2ZEFvpA1WqYm3A@mail.gmail.com>
	<4DA484E1-40FD-4D61-87C4-0F8E511B047F@gmail.com>
Date: Wed, 25 Mar 2015 21:40:35 +0000
Message-ID: 
 <CAKoNANsqY9c=ChdBhHA5xtm=bD8Yc5E=-weO5C6fHPsPHwrxEg@mail.gmail.com>
Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation
From: Raul Kripalani <raul@evosent.com>
To: dev@activemq.apache.org
Content-Type: multipart/alternative; boundary=089e0158cbe2d7f134051223bf1a

--089e0158cbe2d7f134051223bf1a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As an ActiveMQ user and consultant for 7+ years now, I had received the
news of the HornetQ donation quite positively.

AMQ had started to show troubling signs of inactivity. No new exciting
features any longer. Practically no interest in adopting JMS 2.0. In my
head, AMQ had gone into "maintenance mode"  long ago - a fact that's quite
evident if you compare with the vitality of a (somewhat related) community
like Camel.

I confess I have not followed the technical codebase merges, but it did
seem a bit risky to go with v6 for this first release. On a side note, it
doesn't even show seriousness that the v6 wiki page still puts Apollo
forward as core [1].

To me, it feels like a hasty and improvised step. The internals have
changed a great deal, if I'm not mistaken.

Is the community confident enough to go shouting to the world "Hey! This is
our first MAJOR release after 7 years", and have it be a complete success?

Or is the community somewhat making a risky move?

Frankly, given the magnitude of the changes, I would have expected a
timeline of Alpha, Beta and CR releases.  Even if this is not the custom in
this community. Two architectures are being merged, which makes it an
exceptional event. And that deserves exceptional software and release
engineering treatment, if you ask me.

In other words, as an end user, consultant and spokesperson for many
customers, I would expect a series of pre-GA releases with advertisement
and announcements in blogs, online magazines, aggregators, etc. to gather
technical feedback before pushing v6 out the door.

Regards,
Ra=C3=BAl.

[1] http://activemq.apache.org/new-features-in-60.html
On 25 Mar 2015 22:06, "Tracy Snell" <tsnell@gmail.com> wrote:

> I=E2=80=99m fairly certain most of the community is concerned about the f=
uture of
> activemq. It doesn=E2=80=99t follow that HornetQ is the correct choice go=
ing
> forward (it may be but I=E2=80=99ve not seen any consensus on that issue)=
.  The
> current course of naming HornetQ activemq6 seemed like a declaration that
> the community had agreed on what the future was going to look like. In
> reality it looks like 2 communities under one name with one side advocati=
ng
> a join us or say good bye mentality. It is far from evident that not goin=
g
> the HornetQ route will leave ActiveMQ to sink. That=E2=80=99s a bit of an=
 insult to
> the non HornetQ side of this community.
>
> As a user I=E2=80=99m quite excited by the potential benefits of the Horn=
etQ
> donation! I=E2=80=99ve been concerned about the future since Apollo didn=
=E2=80=99t take
> off. The benefits need to be explained, the path forward from 5 to a 6 th=
at
> includes much/all of HornetQ needs to be agreed on and consensus built in
> the community.  Otherwise it just looks like an attempt by HornetQ to tak=
e
> over the ActiveMQ name.
>
>
> > On Mar 25, 2015, at 2:43 PM, Andy Taylor <andy.tayls67@gmail.com
> <mailto:andy.tayls67@gmail.com>> wrote:
> >
> > Rather than the activemq community jumping ship and leaving it to sink =
at
> > some point in the future, let's ensure the future of activemq and its
> > community and actually grow it by bringing 2 communities together by
> having
> > a project tbat everyone could (and should) get behind.
>
>

--089e0158cbe2d7f134051223bf1a--