I must admit that I took Tim's comment (after a moment of reflection) as meaning "we haven't finalised the timeline for our 1.0 release yet" rather than "we don't have any plans to ever release to 1.0".
The only potential external pre-condition we might lace on a 1.0 release is the completion of the AMQP <-> JMS mapping work at OASIS, such that we know we are not going to have to make breaking changes to be in line with that specification. Even there I think we can be (much) less cautious than we were with AMQP 1.0. Since members from the Qpid community are the primary contributors to the OASIS mappng effort, I think we should set ourselves a target for the completion of that work, and also to releasing a 1.0 version of the client within the same timeframe (and that being within this calendar year). -- Rob On 17 January 2017 at 10:49, Gordon Sim <[email protected]> wrote: > On 16/01/17 20:38, Timothy Bish wrote: > >> There are no plans for a 1.0.0 release at this time. >> > > Qpid has historically been reluctant to go to a 1.0 for different reasons. > One was the desire to wait for AMQP 1.0 (which took a long time to come, > but has now been an ISO standard form a long time). Another was in case the > API needed to change. For JMS this wouldn't really be an issue I wouldn't > think. > > So while I have no objection to the current version number, I think we > should not be afraid to move to a 1.0 or beyond. It doesn't mean there are > no more bugs, but it does I think more accurately indicate the level of > completeness and robustness. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
