This is it.. baking...
I will send the voters thread when done.
On Thu, Aug 30, 2018 at 3:21 PM Clebert Suconic
wrote:
>
> I had some issue finishing
> https://github.com/apache/activemq-artemis/pull/2281
>
>
> Now that I finished it.. I'm about to cut it..
>
> I will start the script
I had some issue finishing https://github.com/apache/activemq-artemis/pull/2281
Now that I finished it.. I'm about to cut it..
I will start the script tonight.. so if you have anything to send in,
do it with a git cherry-pick -x into 2.6.x
On Tue, Aug 28, 2018 at 6:58 PM Clebert Suconic
wrote:
I am working on a latest fix I should have sent by tomorrow..
Would anyone have anything else to send it? what about I cut it
tomorrow afternoon (US EST time).?
On Tue, Aug 14, 2018 at 12:24 PM Clebert Suconic
wrote:
>
> Ok.. lets hold it.. and I will work on it.
--
Clebert Suconic
Ok.. lets hold it.. and I will work on it.
me.com> Date: 14/08/2018 06:04 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: HEADS-UP ActiveMQ Artemis 2.6.3 to
> be cut Friday the 10th
> Hi Clebert
> Theres an NPE introduced in
>
> https://github.com/apache/activemq-artemis/commit/
> bf282e5e7d133e898f
) To:
dev@activemq.apache.org Subject: Re: HEADS-UP ActiveMQ Artemis 2.6.3 to be cut
Friday the 10th
Hi Clebert
Theres an NPE introduced inĀ
https://github.com/apache/activemq-artemis/commit/bf282e5e7d133e898f0dc4d08f4df87722fc5a91
I have commented on the PR that was merged that introduced it
message From: Clebert Suconic
Date: 14/08/2018 02:37 (GMT+00:00) To:
dev@activemq.apache.org Subject: Re: HEADS-UP ActiveMQ Artemis 2.6.3 to be cut
Friday the 10th
I fixed the compatibility issue, and a few other PRs merged.
Does anyone see anything else blocking it.. or can we cut
I fixed the compatibility issue, and a few other PRs merged.
Does anyone see anything else blocking it.. or can we cut activemq
artemis 2.6.3 tomorrow?
On Fri, Aug 10, 2018 at 10:06 AM Clebert Suconic
wrote:
>
> I will have to postpone to Monday...
>
> I have started working on a compatibility
I will have to postpone to Monday...
I have started working on a compatibility issue between 1.5 and 2.x
that I want to make sure before we release.
Meanwhile: I have cut a master git report, where I added a XREF of
commits on 2.6.x
this is a current list I just cut of master versus 2.6.x,
I have been cherry-picking everything that makes sense from master into 2.6.x...
I want to have a release cut on Friday/10th. I will start cutting it
on Thurstday the 9th afternoon so the vote is sent Friday Morning (US
EST time)
If you are aware of any blockers for the 2.6.x.. please let me
10 matches
Mail list logo