[JBoss-dev] Re: JBossMQ in JBoss5

[Andrig T Miller]

So what are we doing to get this feature into JBoss Messaging?  If it
isn't already there it has to be put there.  Are you going to make sure
that it gets in?  

It has to be a part of JBoss Messaging 1.2, just so you know.  This is
why JBoss.com development policy is NOT irrelevant.  If JBossMQ starts
to split off from JBoss Messaging from a feature perspective, and we
continue to support it, even if it is optional in AS 5, then we now have
two messaging implementations, that differ in features, that we have to
support for quite a long time, and we have just made our paying
customers lives that much harder to migrate.

I'm okay with allowing this new feature into JBossMQ, based on your
promise, but you need to make sure that it gets into JBoss Messaging
1.2, and it cannot cause that release to slip.

Why is a conversion not an option for some customers?  If the two
releases are feature compatible, and their code doesn't have to change,
I don't see why it wouldn't be an option.  Explain a use case or
scenario here.

Finally, supporting JBossMQ in AS 5 is only the same where the code is
concerned.  By putting it into AS 5, you have extended the amount of
time that it has to be supported substantially.  That directly affects
our cost of support, and shouldn't be looked at only through the lens of
the code.  This is a business decision, not a technical one.

Andy

On Sat, 2006-09-16 at 10:55 +0200, Adrian Brock wrote:

> Encouragement is fine.
> But telling a contributor that his work is useless is not.
> 
> Especially when that reason is based on irrelevant
> JBoss.com development policy that doesn't affect them.
> 
> I already promised him that the work could go in JBoss4
> once he had it working and tested in JBoss5.
> 
> Converting JBossMQ deployments to JBoss Messaging
> deployments is not an option for everybody.
> 
> Forcing such a conversion would just leave certain
> users/customers stuck with JBoss4.
> 
> Supporting JBossMQ within JBoss5 is no different
> to supporting JBossMQ within JBoss4 since it is 
> the same codebase.
> 
> I expect the market to decide that JBoss Messaging
> is better than JBossMQ (it already is, even before
> the upcoming clustering features)
> and the number of JBossMQ users will gradually diminish to zero.
> 
> On Fri, 2006-09-15 at 17:58 +0000, Andrig T Miller wrote:
> > Adrian,
> > 
> >      Every new feature that is developed for JBossMQ has to also be
> > put into JBoss Messaging.  It doesn't matter who does the work, in my
> > mind.  New features of any kind should NOT be put into JBossMQ.  If
> > the community wants to contribute something, they need to be
> > encouraged to contribute to JBoss Messaging.
> > 
> >      On the topic of JBossMQ still being in AS 5, I was not aware that
> > that was an official decision.  If that is the case, that decision
> > needs to be revisted, in my opinion.  I see no reason to have both
> > code bases in AS 5, considering that customers application code is not
> > affected by the change, only server configuration.  I would rather see
> > us take a little time to develop a conversion utility for the
> > migration of the configuration between the two, as part of our
> > productizing AS 5 and JBoss Messaging, then see us support the old
> > code base.
> > 
> > Andy
> > 
> > On Fri, 2006-09-15 at 14:45 +0200, Adrian Brock wrote: 
> > > http://jira.jboss.com/jira/browse/JBAS-2156
> > > plus some others.
> > > 
> > > JBossMQ will be a part of JBoss5.
> > > I've already had to correct this statement on the WIKI before.
> > > 
> > > JBoss Messaging will be the default, JBossMQ will be optional
> > > for those that need to keep using their JBossMQ configuration
> > > within JBoss5.
> > > 
> > > We will remove support for JBossMQ once people have had time
> > > to migrate, i.e. probably JBoss6 or maybe 7 depending upon
> > > when JBoss6 is released.
> > > 
> > > Development of major new features for JBossMQ by JBoss
> > > has already stopped except for those requested by paying customers,
> > > e.g. XARecovery integration with JBossTM is the latest example.
> > > 
> > > That does not preclude development by the community.
> > > 
> > > The example above is a feature provided by the community.
> > > JBoss.com policy towards JBossMQ should not affect this work!
> > Andrig (Andy) Miller
> > VP, Engineering
> > JBoss, a division of Red Hat

Andrig (Andy) Miller
VP, Engineering
JBoss, a division of Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20060918/c9e00162/attachment.html