Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-09 Thread Clebert Suconic
Since I fixed it.. I will try to cut the release today.. will send it out as soon as it's ready any time now. On Thu, Mar 8, 2018 at 7:48 PM, Clebert Suconic wrote: > I think it’s importsnt to fix this bug. I broke it and I want to fix it :) > > On Thu, Mar 8, 2018 at 6:12 PM Timothy Bish wrote

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Clebert Suconic
I think it’s importsnt to fix this bug. I broke it and I want to fix it :) On Thu, Mar 8, 2018 at 6:12 PM Timothy Bish wrote: > On 03/08/2018 05:59 PM, Clebert Suconic wrote: > > I'm pushing this back to monday...I thought that was an easy fix and i > > will need some more tweaking. > > > > > >

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Timothy Bish
On 03/08/2018 05:59 PM, Clebert Suconic wrote: I'm pushing this back to monday...I thought that was an easy fix and i will need some more tweaking. Meanwhile.. @everyone: avoiding pushing anything that will break the release now :) doc fixes and test fixes is of course fine. I'm running the who

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Clebert Suconic
I'm pushing this back to monday...I thought that was an easy fix and i will need some more tweaking. Meanwhile.. @everyone: avoiding pushing anything that will break the release now :) doc fixes and test fixes is of course fine. I'm running the whole testsuite before each PR I send now.. which is

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Clebert Suconic
I'm already on it... i'm working on it. On Thu, Mar 8, 2018 at 8:35 AM, Michael André Pearce wrote: > Can we add > > https://github.com/apache/activemq-artemis/pull/1940 > > As a blocker. > > On reviewing the PR and seeing why this PR is needed/wanted, it seems whilst > console is most visibly a

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Michael André Pearce
Can we add https://github.com/apache/activemq-artemis/pull/1940 As a blocker. On reviewing the PR and seeing why this PR is needed/wanted, it seems whilst console is most visibly affected by a change done , it has more serious effect that the network pinger also seems to get shutdown and not

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-08 Thread Andy Taylor
I think https://issues.apache.org/jira/browse/ARTEMIS-1736 is a blocker as well, Ive just sent a PR with a fix On 7 March 2018 at 04:59, Michael André Pearce wrote: > @Clebert > > Someone in the user threads has raised what looks like a blocker if it’s > real. > > Something to do with large mes

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-06 Thread Michael André Pearce
@Clebert Someone in the user threads has raised what looks like a blocker if it’s real. Something to do with large messages and broker crashing with 2.5.0-SNAPSHOTz Have you seen it? Sent from my iPhone > On 2 Mar 2018, at 23:42, Clebert Suconic wrote: > > If you have anything in mind that

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-02 Thread Clebert Suconic
If you have anything in mind that you consider a blocking. That’s the idea of the heads up. My expectation was the examples. But if you want to request another change, like be PR pending you have that I need to work on ? :) Let me know if you have anything in mind that is a blocker. On Fr

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-01 Thread MichaelAndrePearce
yes a list of blocking tasks, so that we can all focus on those if needed. It sounded like there were a few examples, but it seems like you have that in hand already. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-01 Thread Justin Bertram
I think I've got the examples in good shape. I'm just running a few tests before I send the PR. Justin On Thu, Mar 1, 2018 at 1:28 PM, Clebert Suconic wrote: > My plan was to fix the examples and release it next week. > > If anyone has any tasks that would take an extra 1 or 2 days to > compl

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-01 Thread Clebert Suconic
My plan was to fix the examples and release it next week. If anyone has any tasks that would take an extra 1 or 2 days to complete.. (beyond wed) we could delay (hence I was sending the heads up). We don't need to wait 2 months to make any next release. we could make 2.5.1 in a couple of weeks. I

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-01 Thread Justin Bertram
What do you mean by "things we need to attack"? Tasks to be completed before the release can be done? Justin On Thu, Mar 1, 2018 at 10:42 AM, Michael André Pearce < michael.andre.pea...@me.com> wrote: > Great news. > > Do we have a list of things we need to attack? > > Sent from my iPhone > >

Re: [HEADS-UP] 2.5.0 release some time next week... (after wed)

2018-03-01 Thread Michael André Pearce
Great news. Do we have a list of things we need to attack? Sent from my iPhone > On 1 Mar 2018, at 14:52, Clebert Suconic wrote: > > ${SUBJECT} > > > All we need now is to fix the examples...some are broken... and we > are in a good place for the release I think. > > -- > Clebert Suconic