On 12/02/2014 07:09 PM, Fraser Adams wrote:
It has always felt slightly odd to me that Qpid has never had a version
1.0. I guess that in the back of my mind (and back in the day) I perhaps
assumed that it would hit V1.0 with AMQP 1.0 support, but that didn't
occur.

I guess one thing that might be worth considering is to hold fire on a
change until a couple of significant AMQP 1.0 changes occur - I guess
that the two things that spring to mind would be
1) qpidd making AMQP 0.10 support optional

At present 0-10 support in qpidd can be disabled if desired.

2) availability/maturity of the new Proton based AMQP 1.0 JMS client

Since that is assumed at this point to be separately released anyway, I'm not sure it makes sense for it to impact the version number of other, older and more mature components on a different schedule, unless you are thinking it would be only at that point their 1.0 support could be sufficiently tested.

TBH I don't really know the timeline for these and it might be a bit
moot if they are a long way off, but I've always felt that there was a
fair bit of confusion around the status of AMQP 1.0 JMS support so being
able to deprecate the current interim client feels a fairly significant
step on the maturity of AMQP 1.0 support.

Or is there a Qpid birthday coming up? The project running X years is
probably another reasonable point to trigger a 1.0 release.


TBH I don't think the current numbering system is massively broken, at
the very least it's something that we and most users have got used to.  I
think my personal preference is to pick a sensible point to move to 1.0,
but I'm not going to die in a ditch about any other suggestions.

I feel like for qpidd and qpid::messaging at least, a '1.0' at this point is meaningless and even perhaps confusing. They are both well past that really, placing a high priority on stability and backward compatibility. The 1.0 label to me is more appropriate for newer components like proton, dispatch-router and the new JMS client.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to