Personally I'd probably release that client independently from the rest of
the java tree unless we happened to coincidentally want a patch release of
the rest of the Java tree at the same time.
Post 0.32 I think we are probably thinking of doing incremental patch
releases off the 0.32 branch for
That suggestion works for me in general. The only question would be
around whether the other components in the 'java' tree alongside it
currently would have to be released as well (the broker and other
client would also be deployed curently by the parent 'java build'), or
whether you would trim
So, I'm very much in favour of getting the new client released as soon as
possible.
In terms of the old JMS AMQP 1.0 Client I suggest that post 0.32 we put
this into maintenance mode only... and that as we move to our new
release/directory structure we remove the legacy AMQP 1.0 client and only
.
Robbie
On 18 February 2015 at 22:39, Steve Huston shus...@riverace.com wrote:
-Original Message-
From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Sent: Wednesday, February 18, 2015 10:41 AM
To: users@qpid.apache.org
Subject: Re: towards releasing the new AMQP 1.0 JMS client
On 18
To: users@qpid.apache.org
Subject: Re: towards releasing the new AMQP 1.0 JMS client
On 18 February 2015 at 14:59, Justin Ross justin.r...@gmail.com wrote:
On Wed, Feb 18, 2015 at 7:33 AM, Robbie Gemmell
robbie.gemm...@gmail.com
wrote:
At the moment the version number is 0.1[-SNAPSHOT
On Thu, Feb 19, 2015 at 8:43 AM, Timothy Bish tabish...@gmail.com wrote:
On 02/19/2015 08:01 AM, Robbie Gemmell wrote:
Any more opinions out there on the name/version of the new client? If
not, I'll likely proceed to update the version to 0.1.0[-SNAPSHOT],
leave the module names as
-Original Message-
From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Sent: Wednesday, February 18, 2015 10:41 AM
To: users@qpid.apache.org
Subject: Re: towards releasing the new AMQP 1.0 JMS client
On 18 February 2015 at 14:59, Justin Ross justin.r...@gmail.com wrote:
On Wed
Next up is the name. The new client has thus far been called simply
'Qpid JMS', with module names qpid-jms-foo, and binary tar
apache-qpid-jms[-bin]. We already release two other JMS clients, the
original AMQP 0-x one, module named qpid-client, and the older AMQP
1.0 one, module named
Hi all,
We are getting to the point of wanting to do an initial release of the
new AMQP 1.0 JMS client, which raises some items for discussion.
The quick summary of an email that got quite long is: How do we
version it? What do we name it? How do we handle the overlap with the
older AMQP 1.0 JMS
On 18 February 2015 at 14:59, Justin Ross justin.r...@gmail.com wrote:
On Wed, Feb 18, 2015 at 7:33 AM, Robbie Gemmell robbie.gemm...@gmail.com
wrote:
At the moment the version number is 0.1[-SNAPSHOT], to be followed by
0.2 etc until we think there is sufficient maturity to go 1.0
+1 on,
*. Calling the new JMS impl Qpid JMS.
*. Encouraging new development to use this client.
*. Add a clear note explaining the current situation with our JMS clients.
*. Naming the qpid-amqp-1-0-jms-client to include the word prototype,
which is what it is at best.
Rajith
On Wed, Feb
On Wed, Feb 18, 2015 at 7:33 AM, Robbie Gemmell robbie.gemm...@gmail.com
wrote:
At the moment the version number is 0.1[-SNAPSHOT], to be followed by
0.2 etc until we think there is sufficient maturity to go 1.0
(sidenote: not years :P). The initial focus has been on implementing
the JMS 1.1
On 18 February 2015 at 14:31, Richard Li rich...@datawire.io wrote:
Next up is the name. The new client has thus far been called simply
'Qpid JMS', with module names qpid-jms-foo, and binary tar
apache-qpid-jms[-bin]. We already release two other JMS clients, the
original AMQP 0-x one, module
13 matches
Mail list logo
