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