You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2017/10/27 09:01:03 UTC
Next round of patch releases - Camel 2.19.4 and 2.20.1
Hi
We should start to think about doing the next round of patch releases.
For example start of next month we can cut 2.19.4, and then following
week 2.20.1.
Its always good to get a quick first patch release out when we have
done a big release recently.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
+1 go for it Gregor
On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
> RC within the next minutes. Please ping me if you have any concerns.
>
> Thanks,
> Gregor
>
>
> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>> Hi,
>>
>> would it be possible to wait till tomorrow evening before cutting the
>> 2.20.1 ?
>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001 to fix
>> a race condition for which the camel context may end-up in a deadlock upon
>> component creation.
>>
>> Luca
>>
>>
>>
>> ---
>> Luca Burgazzoli
>>
>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com> wrote:
>>
>>> +1
>>>
>>> for 2.20.1 from wildfly-camel
>>>
>>> — thomas
>>>
>>>
>>> > On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> >
>>> > Hi
>>> >
>>> > We should start to think about doing the next round of patch releases.
>>> > For example start of next month we can cut 2.19.4, and then following
>>> > week 2.20.1.
>>> > Its always good to get a quick first patch release out when we have
>>> > done a big release recently.
>>> >
>>> >
>>> >
>>> > --
>>> > Claus Ibsen
>>> > -----------------
>>> > http://davsclaus.com @davsclaus
>>> > Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Luca Burgazzoli <lb...@gmail.com>.
I need holidays ...
---
Luca Burgazzoli
On Fri, Nov 10, 2017 at 12:48 PM, Gregor Zurowski <gr...@list.zurowski.org>
wrote:
> Hi Babak,
>
> Thanks for pointing this out. I've rename the class on master and
> cherry-picked it onto camel-2.20.x. I am going to cut the RC now.
>
> Thanks,
> Gregor
>
>
> On Fri, Nov 10, 2017 at 12:40 PM, Babak Vahdat
> <ba...@swissonline.ch> wrote:
> > Hi Luca
> >
> > I guess CamelContextDeadlockText should be renamed to
> CamelContextDeadlockTest.
> >
> > Babak
> >
> > Sent from my iPhone...
> >
> >> Am 10.11.2017 um 10:39 schrieb Luca Burgazzoli <lb...@gmail.com>:
> >>
> >> Uh sorry I should have forgot to save the changes. Should be fixed now
> >>
> >>
> >> ---
> >> Luca Burgazzoli
> >>
> >> On Fri, Nov 10, 2017 at 9:59 AM, Gregor Zurowski <
> gregor@list.zurowski.org>
> >> wrote:
> >>
> >>> Hi Luca,
> >>>
> >>> While reviewing your code I realized that something went wrong when
> >>> you added your changes on branch camel-2.20.x:
> >>>
> >>> https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723d
> >>> a50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
> >>>
> >>> Can you please take a look?
> >>>
> >>> Thanks,
> >>> Gregor
> >>>
> >>>
> >>> On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
> >>> <gr...@list.zurowski.org> wrote:
> >>>> Hi Everyone:
> >>>>
> >>>> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
> >>>> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
> >>>> RC within the next minutes. Please ping me if you have any concerns.
> >>>>
> >>>> Thanks,
> >>>> Gregor
> >>>>
> >>>>
> >>>> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <
> lburgazzoli@gmail.com>
> >>> wrote:
> >>>>> Hi,
> >>>>>
> >>>>> would it be possible to wait till tomorrow evening before cutting the
> >>>>> 2.20.1 ?
> >>>>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001
> >>> to fix
> >>>>> a race condition for which the camel context may end-up in a deadlock
> >>> upon
> >>>>> component creation.
> >>>>>
> >>>>> Luca
> >>>>>
> >>>>>
> >>>>>
> >>>>> ---
> >>>>> Luca Burgazzoli
> >>>>>
> >>>>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com>
> >>> wrote:
> >>>>>
> >>>>>> +1
> >>>>>>
> >>>>>> for 2.20.1 from wildfly-camel
> >>>>>>
> >>>>>> — thomas
> >>>>>>
> >>>>>>
> >>>>>>> On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com>
> >>> wrote:
> >>>>>>>
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> We should start to think about doing the next round of patch
> >>> releases.
> >>>>>>> For example start of next month we can cut 2.19.4, and then
> following
> >>>>>>> week 2.20.1.
> >>>>>>> Its always good to get a quick first patch release out when we have
> >>>>>>> done a big release recently.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Claus Ibsen
> >>>>>>> -----------------
> >>>>>>> http://davsclaus.com @davsclaus
> >>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
> >>>>>>
> >>>>>>
> >>>
> >
>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Babak Vahdat <ba...@swissonline.ch>.
Sent from my iPhone...
> Am 10.11.2017 um 12:48 schrieb Gregor Zurowski <gr...@list.zurowski.org>:
>
> Hi Babak,
>
> Thanks for pointing this out. I've rename the class on master and
> cherry-picked it onto camel-2.20.x. I am going to cut the RC now.
>
Hi Gregor
Thanks a lot for the fix and cutting the RC :-)
Babak
> Thanks,
> Gregor
>
>
> On Fri, Nov 10, 2017 at 12:40 PM, Babak Vahdat
> <ba...@swissonline.ch> wrote:
>> Hi Luca
>>
>> I guess CamelContextDeadlockText should be renamed to CamelContextDeadlockTest.
>>
>> Babak
>>
>> Sent from my iPhone...
>>
>>> Am 10.11.2017 um 10:39 schrieb Luca Burgazzoli <lb...@gmail.com>:
>>>
>>> Uh sorry I should have forgot to save the changes. Should be fixed now
>>>
>>>
>>> ---
>>> Luca Burgazzoli
>>>
>>> On Fri, Nov 10, 2017 at 9:59 AM, Gregor Zurowski <gr...@list.zurowski.org>
>>> wrote:
>>>
>>>> Hi Luca,
>>>>
>>>> While reviewing your code I realized that something went wrong when
>>>> you added your changes on branch camel-2.20.x:
>>>>
>>>> https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723d
>>>> a50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
>>>>
>>>> Can you please take a look?
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Everyone:
>>>>>
>>>>> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
>>>>> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
>>>>> RC within the next minutes. Please ping me if you have any concerns.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com>
>>>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> would it be possible to wait till tomorrow evening before cutting the
>>>>>> 2.20.1 ?
>>>>>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001
>>>> to fix
>>>>>> a race condition for which the camel context may end-up in a deadlock
>>>> upon
>>>>>> component creation.
>>>>>>
>>>>>> Luca
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---
>>>>>> Luca Burgazzoli
>>>>>>
>>>>>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com>
>>>> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> for 2.20.1 from wildfly-camel
>>>>>>>
>>>>>>> — thomas
>>>>>>>
>>>>>>>
>>>>>>>> On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com>
>>>> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> We should start to think about doing the next round of patch
>>>> releases.
>>>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>>>> week 2.20.1.
>>>>>>>> Its always good to get a quick first patch release out when we have
>>>>>>>> done a big release recently.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>
>>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Babak,
Thanks for pointing this out. I've rename the class on master and
cherry-picked it onto camel-2.20.x. I am going to cut the RC now.
Thanks,
Gregor
On Fri, Nov 10, 2017 at 12:40 PM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi Luca
>
> I guess CamelContextDeadlockText should be renamed to CamelContextDeadlockTest.
>
> Babak
>
> Sent from my iPhone...
>
>> Am 10.11.2017 um 10:39 schrieb Luca Burgazzoli <lb...@gmail.com>:
>>
>> Uh sorry I should have forgot to save the changes. Should be fixed now
>>
>>
>> ---
>> Luca Burgazzoli
>>
>> On Fri, Nov 10, 2017 at 9:59 AM, Gregor Zurowski <gr...@list.zurowski.org>
>> wrote:
>>
>>> Hi Luca,
>>>
>>> While reviewing your code I realized that something went wrong when
>>> you added your changes on branch camel-2.20.x:
>>>
>>> https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723d
>>> a50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
>>>
>>> Can you please take a look?
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Everyone:
>>>>
>>>> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
>>>> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
>>>> RC within the next minutes. Please ping me if you have any concerns.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com>
>>> wrote:
>>>>> Hi,
>>>>>
>>>>> would it be possible to wait till tomorrow evening before cutting the
>>>>> 2.20.1 ?
>>>>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001
>>> to fix
>>>>> a race condition for which the camel context may end-up in a deadlock
>>> upon
>>>>> component creation.
>>>>>
>>>>> Luca
>>>>>
>>>>>
>>>>>
>>>>> ---
>>>>> Luca Burgazzoli
>>>>>
>>>>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com>
>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> for 2.20.1 from wildfly-camel
>>>>>>
>>>>>> — thomas
>>>>>>
>>>>>>
>>>>>>> On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com>
>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> We should start to think about doing the next round of patch
>>> releases.
>>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>>> week 2.20.1.
>>>>>>> Its always good to get a quick first patch release out when we have
>>>>>>> done a big release recently.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>
>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Luca
I guess CamelContextDeadlockText should be renamed to CamelContextDeadlockTest.
Babak
Sent from my iPhone...
> Am 10.11.2017 um 10:39 schrieb Luca Burgazzoli <lb...@gmail.com>:
>
> Uh sorry I should have forgot to save the changes. Should be fixed now
>
>
> ---
> Luca Burgazzoli
>
> On Fri, Nov 10, 2017 at 9:59 AM, Gregor Zurowski <gr...@list.zurowski.org>
> wrote:
>
>> Hi Luca,
>>
>> While reviewing your code I realized that something went wrong when
>> you added your changes on branch camel-2.20.x:
>>
>> https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723d
>> a50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
>>
>> Can you please take a look?
>>
>> Thanks,
>> Gregor
>>
>>
>> On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Everyone:
>>>
>>> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
>>> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
>>> RC within the next minutes. Please ping me if you have any concerns.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com>
>> wrote:
>>>> Hi,
>>>>
>>>> would it be possible to wait till tomorrow evening before cutting the
>>>> 2.20.1 ?
>>>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001
>> to fix
>>>> a race condition for which the camel context may end-up in a deadlock
>> upon
>>>> component creation.
>>>>
>>>> Luca
>>>>
>>>>
>>>>
>>>> ---
>>>> Luca Burgazzoli
>>>>
>>>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com>
>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> for 2.20.1 from wildfly-camel
>>>>>
>>>>> — thomas
>>>>>
>>>>>
>>>>>> On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com>
>> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> We should start to think about doing the next round of patch
>> releases.
>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>> week 2.20.1.
>>>>>> Its always good to get a quick first patch release out when we have
>>>>>> done a big release recently.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Luca Burgazzoli <lb...@gmail.com>.
Uh sorry I should have forgot to save the changes. Should be fixed now
---
Luca Burgazzoli
On Fri, Nov 10, 2017 at 9:59 AM, Gregor Zurowski <gr...@list.zurowski.org>
wrote:
> Hi Luca,
>
> While reviewing your code I realized that something went wrong when
> you added your changes on branch camel-2.20.x:
>
> https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723d
> a50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
>
> Can you please take a look?
>
> Thanks,
> Gregor
>
>
> On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
> > Hi Everyone:
> >
> > As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
> > going to re-cut the RC for Camel 2.20.1. I am starting to build a new
> > RC within the next minutes. Please ping me if you have any concerns.
> >
> > Thanks,
> > Gregor
> >
> >
> > On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com>
> wrote:
> >> Hi,
> >>
> >> would it be possible to wait till tomorrow evening before cutting the
> >> 2.20.1 ?
> >> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001
> to fix
> >> a race condition for which the camel context may end-up in a deadlock
> upon
> >> component creation.
> >>
> >> Luca
> >>
> >>
> >>
> >> ---
> >> Luca Burgazzoli
> >>
> >> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com>
> wrote:
> >>
> >>> +1
> >>>
> >>> for 2.20.1 from wildfly-camel
> >>>
> >>> — thomas
> >>>
> >>>
> >>> > On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
> >>> >
> >>> > Hi
> >>> >
> >>> > We should start to think about doing the next round of patch
> releases.
> >>> > For example start of next month we can cut 2.19.4, and then following
> >>> > week 2.20.1.
> >>> > Its always good to get a quick first patch release out when we have
> >>> > done a big release recently.
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Claus Ibsen
> >>> > -----------------
> >>> > http://davsclaus.com @davsclaus
> >>> > Camel in Action 2: https://www.manning.com/ibsen2
> >>>
> >>>
>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Luca,
While reviewing your code I realized that something went wrong when
you added your changes on branch camel-2.20.x:
https://github.com/apache/camel/commit/0a5e8910de2c585ca34a8b8444723da50b5e5ec6#diff-e48a0798fb2287dd7a15ae88a0801a58R5
Can you please take a look?
Thanks,
Gregor
On Fri, Nov 10, 2017 at 9:53 AM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
> going to re-cut the RC for Camel 2.20.1. I am starting to build a new
> RC within the next minutes. Please ping me if you have any concerns.
>
> Thanks,
> Gregor
>
>
> On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>> Hi,
>>
>> would it be possible to wait till tomorrow evening before cutting the
>> 2.20.1 ?
>> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001 to fix
>> a race condition for which the camel context may end-up in a deadlock upon
>> component creation.
>>
>> Luca
>>
>>
>>
>> ---
>> Luca Burgazzoli
>>
>> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com> wrote:
>>
>>> +1
>>>
>>> for 2.20.1 from wildfly-camel
>>>
>>> — thomas
>>>
>>>
>>> > On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> >
>>> > Hi
>>> >
>>> > We should start to think about doing the next round of patch releases.
>>> > For example start of next month we can cut 2.19.4, and then following
>>> > week 2.20.1.
>>> > Its always good to get a quick first patch release out when we have
>>> > done a big release recently.
>>> >
>>> >
>>> >
>>> > --
>>> > Claus Ibsen
>>> > -----------------
>>> > http://davsclaus.com @davsclaus
>>> > Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone:
As discuss on https://issues.apache.org/jira/browse/CAMEL-12001, I am
going to re-cut the RC for Camel 2.20.1. I am starting to build a new
RC within the next minutes. Please ping me if you have any concerns.
Thanks,
Gregor
On Thu, Nov 9, 2017 at 6:29 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
> Hi,
>
> would it be possible to wait till tomorrow evening before cutting the
> 2.20.1 ?
> I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001 to fix
> a race condition for which the camel context may end-up in a deadlock upon
> component creation.
>
> Luca
>
>
>
> ---
> Luca Burgazzoli
>
> On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com> wrote:
>
>> +1
>>
>> for 2.20.1 from wildfly-camel
>>
>> — thomas
>>
>>
>> > On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> >
>> > Hi
>> >
>> > We should start to think about doing the next round of patch releases.
>> > For example start of next month we can cut 2.19.4, and then following
>> > week 2.20.1.
>> > Its always good to get a quick first patch release out when we have
>> > done a big release recently.
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Luca Burgazzoli <lb...@gmail.com>.
Hi,
would it be possible to wait till tomorrow evening before cutting the
2.20.1 ?
I'm working to fix https://issues.apache.org/jira/browse/CAMEL-12001 to fix
a race condition for which the camel context may end-up in a deadlock upon
component creation.
Luca
---
Luca Burgazzoli
On Wed, Nov 8, 2017 at 9:42 AM, Thomas Diesler <td...@redhat.com> wrote:
> +1
>
> for 2.20.1 from wildfly-camel
>
> — thomas
>
>
> > On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > We should start to think about doing the next round of patch releases.
> > For example start of next month we can cut 2.19.4, and then following
> > week 2.20.1.
> > Its always good to get a quick first patch release out when we have
> > done a big release recently.
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Thomas Diesler <td...@redhat.com>.
+1
for 2.20.1 from wildfly-camel
— thomas
> On Oct 27, 2017, at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> We should start to think about doing the next round of patch releases.
> For example start of next month we can cut 2.19.4, and then following
> week 2.20.1.
> Its always good to get a quick first patch release out when we have
> done a big release recently.
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Luca Burgazzoli <lb...@gmail.com>.
+1
---
Luca Burgazzoli
On Fri, Oct 27, 2017 at 11:02 AM, Andrea Cosentino <
ancosen1985@yahoo.com.invalid> wrote:
> +1.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, October 27, 2017, 11:01:37 AM GMT+2, Claus Ibsen <
> claus.ibsen@gmail.com> wrote:
>
>
>
>
>
> Hi
>
> We should start to think about doing the next round of patch releases.
> For example start of next month we can cut 2.19.4, and then following
> week 2.20.1.
> Its always good to get a quick first patch release out when we have
> done a big release recently.
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
+1.
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, October 27, 2017, 11:01:37 AM GMT+2, Claus Ibsen <cl...@gmail.com> wrote:
Hi
We should start to think about doing the next round of patch releases.
For example start of next month we can cut 2.19.4, and then following
week 2.20.1.
Its always good to get a quick first patch release out when we have
done a big release recently.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Zoran Regvart <zo...@regvart.com>.
+1
zoran
--
Zoran Regvart
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It sounds good. No objection from my side.
Regards
JB
On Oct 31, 2017, 12:07, at 12:07, Gregor Zurowski <gr...@list.zurowski.org> wrote:
>Hi,
>
>Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>already ready for cutting, or do we need to wait for further changes
>until the weekend?
>
>Thanks,
>Gregor
>
>
>On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com>
>wrote:
>> Hi Gregor
>>
>> I wonder if you would get time for example this coming weekend to cut
>> Camel 2.19.4 release?
>> Then we can follow up with 2.20.1 the next weekend.
>>
>>
>>
>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com>
>wrote:
>>> Hi
>>>
>>> We should start to think about doing the next round of patch
>releases.
>>> For example start of next month we can cut 2.19.4, and then
>following
>>> week 2.20.1.
>>> Its always good to get a quick first patch release out when we have
>>> done a big release recently.
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
+1, Thanks Gregor.
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, October 31, 2017, 12:07:48 PM GMT+1, Gregor Zurowski <gr...@list.zurowski.org> wrote:
Hi,
Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
already ready for cutting, or do we need to wait for further changes
until the weekend?
Thanks,
Gregor
On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> I wonder if you would get time for example this coming weekend to cut
> Camel 2.19.4 release?
> Then we can follow up with 2.20.1 the next weekend.
>
>
>
> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> We should start to think about doing the next round of patch releases.
>> For example start of next month we can cut 2.19.4, and then following
>> week 2.20.1.
>> Its always good to get a quick first patch release out when we have
>> done a big release recently.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor
CXF has been upgraded, so the 2.20.x branch should be ready for the RC
On Mon, Nov 6, 2017 at 9:50 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> Its almost ready. There is a new CXF 3.2.1 release on the way (in vote
> now). It would be good IMHO to upgrade to this version.
>
> http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-3-2-1-and-3-1-14-patch-releases-td5784846.html
> https://issues.apache.org/jira/browse/CAMEL-11993
>
> When that is upgraded, then I think we are ready.
>
> On Sun, Nov 5, 2017 at 12:41 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Everyone:
>>
>> I am currently releasing 2.19.4 and wondered whether the 2.20.x branch
>> is ready for the 2.20.1 release candidate?
>>
>> Thanks,
>> Gregor
>>
>>
>> On Tue, Oct 31, 2017 at 1:55 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> Yeah I have just pushed the fix to branches.
>>> So the 2.19.x branch should be ready for cutting a release.
>>>
>>>
>>>
>>> On Tue, Oct 31, 2017 at 1:11 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Claus,
>>>>
>>>> Alright, if we are good to cut after the backport of CAMEL-11967, I'd
>>>> start with it tonight.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Tue, Oct 31, 2017 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>>>>>> already ready for cutting, or do we need to wait for further changes
>>>>>> until the weekend?
>>>>>>
>>>>>
>>>>> I am working on a fix for CAMEL-11967 to be backported.
>>>>> I will get that fixed soon, and write back here.
>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi Gregor
>>>>>>>
>>>>>>> I wonder if you would get time for example this coming weekend to cut
>>>>>>> Camel 2.19.4 release?
>>>>>>> Then we can follow up with 2.20.1 the next weekend.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> We should start to think about doing the next round of patch releases.
>>>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>>>> week 2.20.1.
>>>>>>>> Its always good to get a quick first patch release out when we have
>>>>>>>> done a big release recently.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor
Its almost ready. There is a new CXF 3.2.1 release on the way (in vote
now). It would be good IMHO to upgrade to this version.
http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-3-2-1-and-3-1-14-patch-releases-td5784846.html
https://issues.apache.org/jira/browse/CAMEL-11993
When that is upgraded, then I think we are ready.
On Sun, Nov 5, 2017 at 12:41 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> I am currently releasing 2.19.4 and wondered whether the 2.20.x branch
> is ready for the 2.20.1 release candidate?
>
> Thanks,
> Gregor
>
>
> On Tue, Oct 31, 2017 at 1:55 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> Yeah I have just pushed the fix to branches.
>> So the 2.19.x branch should be ready for cutting a release.
>>
>>
>>
>> On Tue, Oct 31, 2017 at 1:11 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> Alright, if we are good to cut after the backport of CAMEL-11967, I'd
>>> start with it tonight.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Tue, Oct 31, 2017 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi,
>>>>>
>>>>> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>>>>> already ready for cutting, or do we need to wait for further changes
>>>>> until the weekend?
>>>>>
>>>>
>>>> I am working on a fix for CAMEL-11967 to be backported.
>>>> I will get that fixed soon, and write back here.
>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> I wonder if you would get time for example this coming weekend to cut
>>>>>> Camel 2.19.4 release?
>>>>>> Then we can follow up with 2.20.1 the next weekend.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> We should start to think about doing the next round of patch releases.
>>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>>> week 2.20.1.
>>>>>>> Its always good to get a quick first patch release out when we have
>>>>>>> done a big release recently.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone:
I am currently releasing 2.19.4 and wondered whether the 2.20.x branch
is ready for the 2.20.1 release candidate?
Thanks,
Gregor
On Tue, Oct 31, 2017 at 1:55 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> Yeah I have just pushed the fix to branches.
> So the 2.19.x branch should be ready for cutting a release.
>
>
>
> On Tue, Oct 31, 2017 at 1:11 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Claus,
>>
>> Alright, if we are good to cut after the backport of CAMEL-11967, I'd
>> start with it tonight.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Tue, Oct 31, 2017 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi,
>>>>
>>>> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>>>> already ready for cutting, or do we need to wait for further changes
>>>> until the weekend?
>>>>
>>>
>>> I am working on a fix for CAMEL-11967 to be backported.
>>> I will get that fixed soon, and write back here.
>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> I wonder if you would get time for example this coming weekend to cut
>>>>> Camel 2.19.4 release?
>>>>> Then we can follow up with 2.20.1 the next weekend.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> We should start to think about doing the next round of patch releases.
>>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>>> week 2.20.1.
>>>>>> Its always good to get a quick first patch release out when we have
>>>>>> done a big release recently.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor
Yeah I have just pushed the fix to branches.
So the 2.19.x branch should be ready for cutting a release.
On Tue, Oct 31, 2017 at 1:11 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Claus,
>
> Alright, if we are good to cut after the backport of CAMEL-11967, I'd
> start with it tonight.
>
> Thanks,
> Gregor
>
>
> On Tue, Oct 31, 2017 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi,
>>>
>>> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>>> already ready for cutting, or do we need to wait for further changes
>>> until the weekend?
>>>
>>
>> I am working on a fix for CAMEL-11967 to be backported.
>> I will get that fixed soon, and write back here.
>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> I wonder if you would get time for example this coming weekend to cut
>>>> Camel 2.19.4 release?
>>>> Then we can follow up with 2.20.1 the next weekend.
>>>>
>>>>
>>>>
>>>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> We should start to think about doing the next round of patch releases.
>>>>> For example start of next month we can cut 2.19.4, and then following
>>>>> week 2.20.1.
>>>>> Its always good to get a quick first patch release out when we have
>>>>> done a big release recently.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Claus,
Alright, if we are good to cut after the backport of CAMEL-11967, I'd
start with it tonight.
Thanks,
Gregor
On Tue, Oct 31, 2017 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
> On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi,
>>
>> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
>> already ready for cutting, or do we need to wait for further changes
>> until the weekend?
>>
>
> I am working on a fix for CAMEL-11967 to be backported.
> I will get that fixed soon, and write back here.
>
>> Thanks,
>> Gregor
>>
>>
>> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> I wonder if you would get time for example this coming weekend to cut
>>> Camel 2.19.4 release?
>>> Then we can follow up with 2.20.1 the next weekend.
>>>
>>>
>>>
>>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> We should start to think about doing the next round of patch releases.
>>>> For example start of next month we can cut 2.19.4, and then following
>>>> week 2.20.1.
>>>> Its always good to get a quick first patch release out when we have
>>>> done a big release recently.
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Oct 31, 2017 at 12:07 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi,
>
> Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
> already ready for cutting, or do we need to wait for further changes
> until the weekend?
>
I am working on a fix for CAMEL-11967 to be backported.
I will get that fixed soon, and write back here.
> Thanks,
> Gregor
>
>
> On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> I wonder if you would get time for example this coming weekend to cut
>> Camel 2.19.4 release?
>> Then we can follow up with 2.20.1 the next weekend.
>>
>>
>>
>> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> We should start to think about doing the next round of patch releases.
>>> For example start of next month we can cut 2.19.4, and then following
>>> week 2.20.1.
>>> Its always good to get a quick first patch release out when we have
>>> done a big release recently.
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi,
Yes, I can cut the release candidate for Camel 2.19.4. Is the branch
already ready for cutting, or do we need to wait for further changes
until the weekend?
Thanks,
Gregor
On Tue, Oct 31, 2017 at 8:07 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> I wonder if you would get time for example this coming weekend to cut
> Camel 2.19.4 release?
> Then we can follow up with 2.20.1 the next weekend.
>
>
>
> On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> We should start to think about doing the next round of patch releases.
>> For example start of next month we can cut 2.19.4, and then following
>> week 2.20.1.
>> Its always good to get a quick first patch release out when we have
>> done a big release recently.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Next round of patch releases - Camel 2.19.4 and 2.20.1
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor
I wonder if you would get time for example this coming weekend to cut
Camel 2.19.4 release?
Then we can follow up with 2.20.1 the next weekend.
On Fri, Oct 27, 2017 at 11:01 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> We should start to think about doing the next round of patch releases.
> For example start of next month we can cut 2.19.4, and then following
> week 2.20.1.
> Its always good to get a quick first patch release out when we have
> done a big release recently.
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2