Re: Cutting a 5.9.1 release??

2014-01-15 Thread Robert Davies
So removing something as visual as a console should be a point release (5.10) - and we have a large number of critical issues open (currently 20) - we should try get those resolved or properly assessed. Hopefully we can get 5.10 out really quickly. On 15 Jan 2014, at 21:44, Hadrian Zbarcea w

Re: Cutting a 5.9.1 release??

2014-01-15 Thread Hadrian Zbarcea
The issue is now fixed. Time to finally cut 5.9.1? I volunteer to do it if no objections or other takers. Hadrian On 01/02/2014 04:28 PM, Daniel Kulp wrote: On Dec 30, 2013, at 7:30 AM, Joshua Watkins wrote: This topic seems to have stalled. Is the release still waiting on something?

Re: Cutting a 5.9.1 release??

2014-01-02 Thread Daniel Kulp
On Dec 30, 2013, at 7:30 AM, Joshua Watkins wrote: This topic seems to have stalled. Is the release still waiting on > something? I *think* there were a couple remaining things: 1) Removing the hawt.io stuff to meet Apache requirements. I submitted a pull request for this today. Hopefully

Re: Cutting a 5.9.1 release??

2013-12-30 Thread Joshua Watkins
This topic seems to have stalled. Is the release still waiting on something? Regards, Josh On 11/12/2013 16:23, "Dejan Bosanac" wrote: >https://issues.apache.org/jira/browse/AMQ-4909 is now fixed. > >Regards >-- >Dejan Bosanac >-- >Red Hat, Inc. >FuseSource is now part of

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Dejan Bosanac
https://issues.apache.org/jira/browse/AMQ-4909 is now fixed. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Dec 11, 2013 at 1

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Dejan Bosanac
Or just explain upgrade path it in release notes. I'll get it fixed now. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Dec 1

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Robert Davies
Why not just go for a 5.10 and get this fixed ? On 11 Dec 2013, at 11:13, Dejan Bosanac wrote: > I agree with this. We should remove activemq-camel from activemq-osgi and > use it as a separate bundle. I'm not sure though if it's a good fix for a > minor release as we need to change features as

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Robert Davies
All good from me now On 11 Dec 2013, at 10:43, Dejan Bosanac wrote: > All good on my side. > > Regards > -- > Dejan Bosanac > -- > Red Hat, Inc. > FuseSource is now part of Red Hat > dbosa...@redhat.com > Twitter: @dejanb > Blog: http://sensatic.net > ActiveMQ in Action: htt

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Dejan Bosanac
I agree with this. We should remove activemq-camel from activemq-osgi and use it as a separate bundle. I'm not sure though if it's a good fix for a minor release as we need to change features as well. Also upgrade from 5.9.0 to 5.9.1 in karat would mean you need to upgrade activemq-osgi and add act

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Raul Kripalani
Hi, Would there be a chance to take a look at https://issues.apache.org/jira/browse/AMQ-4909 for the 5.9.1 release? This is a blocker that prevents users from upgrading the AMQ broker within an Karaf / ServiceMix container, if they also use Camel. Try upgrading from AMQ 5.8 to 5.9, and you get C

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Robert Davies
Hopefully get this fixed in the next hour or so On 10 Dec 2013, at 17:31, Robert Davies wrote: > I’m having a look at AMQ-4924 - but that can wait till 5.10 - presumably that > won’t be far away ? > > On 10 Dec 2013, at 17:28, Hiram Chirino wrote: > >> How we looking for 5.9.1 release? I'm h

Re: Cutting a 5.9.1 release??

2013-12-11 Thread Dejan Bosanac
All good on my side. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Dec 10, 2013 at 6:31 PM, Robert Davies wrote: > I’m hav

Re: Cutting a 5.9.1 release??

2013-12-10 Thread Robert Davies
I’m having a look at AMQ-4924 - but that can wait till 5.10 - presumably that won’t be far away ? On 10 Dec 2013, at 17:28, Hiram Chirino wrote: > How we looking for 5.9.1 release? I'm happy now with how the leveldb > bits are looking. Any outstanding bits left to do? > > -- > Hiram Chirino

Cutting a 5.9.1 release??

2013-12-10 Thread Hiram Chirino
How we looking for 5.9.1 release? I'm happy now with how the leveldb bits are looking. Any outstanding bits left to do? -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino blog: Hiram Chirino's Bit Mojo

Re: Cutting a 5.9.1 release

2013-12-02 Thread dantran
Ping :-) -- View this message in context: http://activemq.2283324.n4.nabble.com/Cutting-a-5-9-1-release-tp4674455p4674997.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Cutting a 5.9.1 release

2013-11-15 Thread Claus Ibsen
+1 On Thu, Nov 14, 2013 at 4:29 PM, Hiram Chirino wrote: > So what do you guys think about doing a quick 5.9.1 release. There > were some big bugs in the 5.9.0 release that have now been fixed and > perhaps we should cut a release now before any major changes make > their way into trunk? > > Wha

Re: Cutting a 5.9.1 release

2013-11-14 Thread Robert Davies
sounds good - there’s some compliance issues with MQTT - I see if I can squeeze those in. On 14 Nov 2013, at 15:29, Hiram Chirino wrote: > So what do you guys think about doing a quick 5.9.1 release. There > were some big bugs in the 5.9.0 release that have now been fixed and > perhaps we shou

Re: Cutting a 5.9.1 release

2013-11-14 Thread Jean-Baptiste Onofré
FYI, about Karaf/OSGi integration, I have the following patches to submit: - instead of depending to the jetty feature, ActiveMQ feature should depend to the http feature. It will allow to easily migrate to Karaf 3.0.0. - extends the ActiveMQ Karaf commands package import version range to suppor

Re: Cutting a 5.9.1 release

2013-11-14 Thread Christian Posta
+1 .. let's do it On Thu, Nov 14, 2013 at 7:59 AM, Timothy Bish wrote: > On 11/14/2013 10:29 AM, Hiram Chirino wrote: >> >> So what do you guys think about doing a quick 5.9.1 release. There >> were some big bugs in the 5.9.0 release that have now been fixed and >> perhaps we should cut a releas

Re: Cutting a 5.9.1 release

2013-11-14 Thread Timothy Bish
On 11/14/2013 10:29 AM, Hiram Chirino wrote: So what do you guys think about doing a quick 5.9.1 release. There were some big bugs in the 5.9.0 release that have now been fixed and perhaps we should cut a release now before any major changes make their way into trunk? What do ya guys think?

Re: Cutting a 5.9.1 release

2013-11-14 Thread Jean-Baptiste Onofré
+1 for the Apache branding in hawt.io as well. Regards JB On 11/14/2013 04:45 PM, Dejan Bosanac wrote: +1 as well. It'd be good to do an apache branding for hawtio as well. I'd hope I can jump to that in the next couple of days. Regards -- Dejan Bosanac -- Red Hat, Inc. Fus

Re: Cutting a 5.9.1 release

2013-11-14 Thread Dejan Bosanac
+1 as well. It'd be good to do an apache branding for hawtio as well. I'd hope I can jump to that in the next couple of days. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in A

Re: Cutting a 5.9.1 release

2013-11-14 Thread Jean-Baptiste Onofré
Hi Hiram, I'm fully agree. I have some fix about OSGi and Karaf integration as well (preparing the support of Karaf 3). I can commit that tomorrow. Regards JB On 11/14/2013 04:29 PM, Hiram Chirino wrote: So what do you guys think about doing a quick 5.9.1 release. There were some big bugs

Cutting a 5.9.1 release

2013-11-14 Thread Hiram Chirino
So what do you guys think about doing a quick 5.9.1 release. There were some big bugs in the 5.9.0 release that have now been fixed and perhaps we should cut a release now before any major changes make their way into trunk? What do ya guys think? -- Hiram Chirino Engineering | Red Hat, Inc.