Apache Camel 2.21.2 patch release

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

Apache Camel 2.21.2 patch release

Claus Ibsen-2
Hi

After the Camel 2.22.0 release, then I think we should work on getting
a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
JIRAs fixed for this version and we will get a couple of more which
are pending to be backported.



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
+1 

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Tuesday, July 3, 2018, 2:09:42 PM GMT+2, Claus Ibsen <[hidden email]> wrote:





Hi

After the Camel 2.22.0 release, then I think we should work on getting
a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
JIRAs fixed for this version and we will get a couple of more which
are pending to be backported.



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Gregor Zurowski-2
In reply to this post by Claus Ibsen-2
Sure, I can take care of the release this weekend.

Thanks,
Gregor


On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:

> Hi
>
> After the Camel 2.22.0 release, then I think we should work on getting
> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
> JIRAs fixed for this version and we will get a couple of more which
> are pending to be backported.
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Gregor Zurowski-2
Hi,

Unfortunately I was not able to cut the release due to the following
problems with the Git repository when trying to push changes:

remote: This repository has been locked due to synchronization issues:
remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
and prevents pushes.
remote: This could either be a benign issue, or the repositories could
be out of sync.
remote: Please contact [hidden email] to have infrastructure
resolve the issue.
remote:
To https://gitbox.apache.org/repos/asf/camel.git
 ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
hook declined)
error: failed to push some refs to
'https://gitbox.apache.org/repos/asf/camel.git'

Did anybody experience this in the past?

Thanks in advance,
Gregor


On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
<[hidden email]> wrote:

> Sure, I can take care of the release this weekend.
>
> Thanks,
> Gregor
>
>
> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:
>> Hi
>>
>> After the Camel 2.22.0 release, then I think we should work on getting
>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
>> JIRAs fixed for this version and we will get a couple of more which
>> are pending to be backported.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Willem.Jiang
Administrator
Hi Gregor,

I just triggered the git sync from the selfservice[1] .
Can you check if the issue is still there?

If the issue is still there you may need ping for infra team by sending the
email to [hidden email]
If you cannot get the response in few hours, you may use the Hipchat[2] to
find the support from infra through the chat.

[1]https://selfserve.apache.org
[2]http://infra.chat/


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Jul 9, 2018 at 3:58 AM, Gregor Zurowski <[hidden email]>
wrote:

> Hi,
>
> Unfortunately I was not able to cut the release due to the following
> problems with the Git repository when trying to push changes:
>
> remote: This repository has been locked due to synchronization issues:
> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
> and prevents pushes.
> remote: This could either be a benign issue, or the repositories could
> be out of sync.
> remote: Please contact [hidden email] to have infrastructure
> resolve the issue.
> remote:
> To https://gitbox.apache.org/repos/asf/camel.git
>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> hook declined)
> error: failed to push some refs to
> 'https://gitbox.apache.org/repos/asf/camel.git'
>
> Did anybody experience this in the past?
>
> Thanks in advance,
> Gregor
>
>
> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> <[hidden email]> wrote:
> > Sure, I can take care of the release this weekend.
> >
> > Thanks,
> > Gregor
> >
> >
> > On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> wrote:
> >> Hi
> >>
> >> After the Camel 2.22.0 release, then I think we should work on getting
> >> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
> >> JIRAs fixed for this version and we will get a couple of more which
> >> are pending to be backported.
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Claus Ibsen-2
In reply to this post by Gregor Zurowski-2
Hi

We need to hold the release until we get this either reverted or find
out why it causes some existing unit tests to fail
https://issues.apache.org/jira/browse/CAMEL-12610



On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
<[hidden email]> wrote:

> Hi,
>
> Unfortunately I was not able to cut the release due to the following
> problems with the Git repository when trying to push changes:
>
> remote: This repository has been locked due to synchronization issues:
> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
> and prevents pushes.
> remote: This could either be a benign issue, or the repositories could
> be out of sync.
> remote: Please contact [hidden email] to have infrastructure
> resolve the issue.
> remote:
> To https://gitbox.apache.org/repos/asf/camel.git
>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> hook declined)
> error: failed to push some refs to
> 'https://gitbox.apache.org/repos/asf/camel.git'
>
> Did anybody experience this in the past?
>
> Thanks in advance,
> Gregor
>
>
> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> <[hidden email]> wrote:
>> Sure, I can take care of the release this weekend.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:
>>> Hi
>>>
>>> After the Camel 2.22.0 release, then I think we should work on getting
>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
>>> JIRAs fixed for this version and we will get a couple of more which
>>> are pending to be backported.
>>>
>>>
>>>
>>> --
>>> 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
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
I vote for reverting it for the moment and move to the next minor release.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <[hidden email]> wrote:





Hi

We need to hold the release until we get this either reverted or find
out why it causes some existing unit tests to fail
https://issues.apache.org/jira/browse/CAMEL-12610



On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
<[hidden email]> wrote:

> Hi,
>
> Unfortunately I was not able to cut the release due to the following
> problems with the Git repository when trying to push changes:
>
> remote: This repository has been locked due to synchronization issues:
> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
> and prevents pushes.
> remote: This could either be a benign issue, or the repositories could
> be out of sync.
> remote: Please contact [hidden email] to have infrastructure
> resolve the issue.
> remote:
> To https://gitbox.apache.org/repos/asf/camel.git
>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> hook declined)
> error: failed to push some refs to
> 'https://gitbox.apache.org/repos/asf/camel.git'
>
> Did anybody experience this in the past?
>
> Thanks in advance,
> Gregor
>
>
> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> <[hidden email]> wrote:
>> Sure, I can take care of the release this weekend.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:
>>> Hi
>>>
>>> After the Camel 2.22.0 release, then I think we should work on getting
>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
>>> JIRAs fixed for this version and we will get a couple of more which
>>> are pending to be backported.
>>>
>>>
>>>
>>> --
>>> 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
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Claus Ibsen-2
Hi

I am taking a look and working on either an improved fix or going to revert.
The issue is that the bean in use is a bit "wrong" as it implements
Processor which you should not really do.


On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
<[hidden email]> wrote:

> I vote for reverting it for the moment and move to the next minor release.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <[hidden email]> wrote:
>
>
>
>
>
> Hi
>
> We need to hold the release until we get this either reverted or find
> out why it causes some existing unit tests to fail
> https://issues.apache.org/jira/browse/CAMEL-12610
>
>
>
> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> <[hidden email]> wrote:
>> Hi,
>>
>> Unfortunately I was not able to cut the release due to the following
>> problems with the Git repository when trying to push changes:
>>
>> remote: This repository has been locked due to synchronization issues:
>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
>> and prevents pushes.
>> remote: This could either be a benign issue, or the repositories could
>> be out of sync.
>> remote: Please contact [hidden email] to have infrastructure
>> resolve the issue.
>> remote:
>> To https://gitbox.apache.org/repos/asf/camel.git
>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
>> hook declined)
>> error: failed to push some refs to
>> 'https://gitbox.apache.org/repos/asf/camel.git'
>>
>> Did anybody experience this in the past?
>>
>> Thanks in advance,
>> Gregor
>>
>>
>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
>> <[hidden email]> wrote:
>>> Sure, I can take care of the release this weekend.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:
>>>> Hi
>>>>
>>>> After the Camel 2.22.0 release, then I think we should work on getting
>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
>>>> JIRAs fixed for this version and we will get a couple of more which
>>>> are pending to be backported.
>>>>
>>>>
>>>>
>>>> --
>>>> 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
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Claus Ibsen-2
Hi

I could not find a better solution so we reverted, but kept a similar
unit test with a regular bean (not impl processor).

I think the branch is potentially ready for a release.

On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]> wrote:

> Hi
>
> I am taking a look and working on either an improved fix or going to revert.
> The issue is that the bean in use is a bit "wrong" as it implements
> Processor which you should not really do.
>
>
> On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> <[hidden email]> wrote:
>> I vote for reverting it for the moment and move to the next minor release.
>>
>> --
>> Andrea Cosentino
>> ----------------------------------
>> Apache Camel PMC Chair
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: [hidden email]
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <[hidden email]> wrote:
>>
>>
>>
>>
>>
>> Hi
>>
>> We need to hold the release until we get this either reverted or find
>> out why it causes some existing unit tests to fail
>> https://issues.apache.org/jira/browse/CAMEL-12610
>>
>>
>>
>> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
>> <[hidden email]> wrote:
>>> Hi,
>>>
>>> Unfortunately I was not able to cut the release due to the following
>>> problems with the Git repository when trying to push changes:
>>>
>>> remote: This repository has been locked due to synchronization issues:
>>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
>>> and prevents pushes.
>>> remote: This could either be a benign issue, or the repositories could
>>> be out of sync.
>>> remote: Please contact [hidden email] to have infrastructure
>>> resolve the issue.
>>> remote:
>>> To https://gitbox.apache.org/repos/asf/camel.git
>>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
>>> hook declined)
>>> error: failed to push some refs to
>>> 'https://gitbox.apache.org/repos/asf/camel.git'
>>>
>>> Did anybody experience this in the past?
>>>
>>> Thanks in advance,
>>> Gregor
>>>
>>>
>>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
>>> <[hidden email]> wrote:
>>>> Sure, I can take care of the release this weekend.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]> wrote:
>>>>> Hi
>>>>>
>>>>> After the Camel 2.22.0 release, then I think we should work on getting
>>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
>>>>> JIRAs fixed for this version and we will get a couple of more which
>>>>> are pending to be backported.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Willem.Jiang
Administrator
I'm sorry for the regression issue.  +1 for reverting the patch to avoid
blocking the release.
But we still find a way to address the cached bean issue, as the bean could
be changed dynamically.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]> wrote:

> Hi
>
> I could not find a better solution so we reverted, but kept a similar
> unit test with a regular bean (not impl processor).
>
> I think the branch is potentially ready for a release.
>
> On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> wrote:
> > Hi
> >
> > I am taking a look and working on either an improved fix or going to
> revert.
> > The issue is that the bean in use is a bit "wrong" as it implements
> > Processor which you should not really do.
> >
> >
> > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > <[hidden email]> wrote:
> >> I vote for reverting it for the moment and move to the next minor
> release.
> >>
> >> --
> >> Andrea Cosentino
> >> ----------------------------------
> >> Apache Camel PMC Chair
> >> Apache Karaf Committer
> >> Apache Servicemix PMC Member
> >> Email: [hidden email]
> >> Twitter: @oscerd2
> >> Github: oscerd
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> [hidden email]> wrote:
> >>
> >>
> >>
> >>
> >>
> >> Hi
> >>
> >> We need to hold the release until we get this either reverted or find
> >> out why it causes some existing unit tests to fail
> >> https://issues.apache.org/jira/browse/CAMEL-12610
> >>
> >>
> >>
> >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> >> <[hidden email]> wrote:
> >>> Hi,
> >>>
> >>> Unfortunately I was not able to cut the release due to the following
> >>> problems with the Git repository when trying to push changes:
> >>>
> >>> remote: This repository has been locked due to synchronization issues:
> >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous error,
> >>> and prevents pushes.
> >>> remote: This could either be a benign issue, or the repositories could
> >>> be out of sync.
> >>> remote: Please contact [hidden email] to have infrastructure
> >>> resolve the issue.
> >>> remote:
> >>> To https://gitbox.apache.org/repos/asf/camel.git
> >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> >>> hook declined)
> >>> error: failed to push some refs to
> >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> >>>
> >>> Did anybody experience this in the past?
> >>>
> >>> Thanks in advance,
> >>> Gregor
> >>>
> >>>
> >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> >>> <[hidden email]> wrote:
> >>>> Sure, I can take care of the release this weekend.
> >>>>
> >>>> Thanks,
> >>>> Gregor
> >>>>
> >>>>
> >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> wrote:
> >>>>> Hi
> >>>>>
> >>>>> After the Camel 2.22.0 release, then I think we should work on
> getting
> >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38
> >>>>> JIRAs fixed for this version and we will get a couple of more which
> >>>>> are pending to be backported.
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

onders-2
Hi,

We have build failing on 2.22.x branch in the last two builds.

https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/

https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/

Fyi.


On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
wrote:

> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> blocking the release.
> But we still find a way to address the cached bean issue, as the bean could
> be changed dynamically.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> wrote:
>
> > Hi
> >
> > I could not find a better solution so we reverted, but kept a similar
> > unit test with a regular bean (not impl processor).
> >
> > I think the branch is potentially ready for a release.
> >
> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > wrote:
> > > Hi
> > >
> > > I am taking a look and working on either an improved fix or going to
> > revert.
> > > The issue is that the bean in use is a bit "wrong" as it implements
> > > Processor which you should not really do.
> > >
> > >
> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > <[hidden email]> wrote:
> > >> I vote for reverting it for the moment and move to the next minor
> > release.
> > >>
> > >> --
> > >> Andrea Cosentino
> > >> ----------------------------------
> > >> Apache Camel PMC Chair
> > >> Apache Karaf Committer
> > >> Apache Servicemix PMC Member
> > >> Email: [hidden email]
> > >> Twitter: @oscerd2
> > >> Github: oscerd
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > [hidden email]> wrote:
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Hi
> > >>
> > >> We need to hold the release until we get this either reverted or find
> > >> out why it causes some existing unit tests to fail
> > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > >>
> > >>
> > >>
> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > >> <[hidden email]> wrote:
> > >>> Hi,
> > >>>
> > >>> Unfortunately I was not able to cut the release due to the following
> > >>> problems with the Git repository when trying to push changes:
> > >>>
> > >>> remote: This repository has been locked due to synchronization
> issues:
> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> error,
> > >>> and prevents pushes.
> > >>> remote: This could either be a benign issue, or the repositories
> could
> > >>> be out of sync.
> > >>> remote: Please contact [hidden email] to have infrastructure
> > >>> resolve the issue.
> > >>> remote:
> > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > >>> hook declined)
> > >>> error: failed to push some refs to
> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > >>>
> > >>> Did anybody experience this in the past?
> > >>>
> > >>> Thanks in advance,
> > >>> Gregor
> > >>>
> > >>>
> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > >>> <[hidden email]> wrote:
> > >>>> Sure, I can take care of the release this weekend.
> > >>>>
> > >>>> Thanks,
> > >>>> Gregor
> > >>>>
> > >>>>
> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> > wrote:
> > >>>>> Hi
> > >>>>>
> > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > getting
> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
> 38
> > >>>>> JIRAs fixed for this version and we will get a couple of more which
> > >>>>> are pending to be backported.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
They seem to be sporadic errors, because between 18 and 19 there weren't changes to the code base. Lets keep an eye on this job.

Thanks Onder.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:





Hi,

We have build failing on 2.22.x branch in the last two builds.

https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/

https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/

Fyi.


On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
wrote:

> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> blocking the release.
> But we still find a way to address the cached bean issue, as the bean could
> be changed dynamically.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> wrote:
>
> > Hi
> >
> > I could not find a better solution so we reverted, but kept a similar
> > unit test with a regular bean (not impl processor).
> >
> > I think the branch is potentially ready for a release.
> >
> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > wrote:
> > > Hi
> > >
> > > I am taking a look and working on either an improved fix or going to
> > revert.
> > > The issue is that the bean in use is a bit "wrong" as it implements
> > > Processor which you should not really do.
> > >
> > >
> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > <[hidden email]> wrote:
> > >> I vote for reverting it for the moment and move to the next minor
> > release.
> > >>
> > >> --
> > >> Andrea Cosentino
> > >> ----------------------------------
> > >> Apache Camel PMC Chair
> > >> Apache Karaf Committer
> > >> Apache Servicemix PMC Member
> > >> Email: [hidden email]
> > >> Twitter: @oscerd2
> > >> Github: oscerd
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > [hidden email]> wrote:
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Hi
> > >>
> > >> We need to hold the release until we get this either reverted or find
> > >> out why it causes some existing unit tests to fail
> > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > >>
> > >>
> > >>
> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > >> <[hidden email]> wrote:
> > >>> Hi,
> > >>>
> > >>> Unfortunately I was not able to cut the release due to the following
> > >>> problems with the Git repository when trying to push changes:
> > >>>
> > >>> remote: This repository has been locked due to synchronization
> issues:
> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> error,
> > >>> and prevents pushes.
> > >>> remote: This could either be a benign issue, or the repositories
> could
> > >>> be out of sync.
> > >>> remote: Please contact [hidden email] to have infrastructure
> > >>> resolve the issue.
> > >>> remote:
> > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > >>> hook declined)
> > >>> error: failed to push some refs to
> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > >>>
> > >>> Did anybody experience this in the past?
> > >>>
> > >>> Thanks in advance,
> > >>> Gregor
> > >>>
> > >>>
> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > >>> <[hidden email]> wrote:
> > >>>> Sure, I can take care of the release this weekend.
> > >>>>
> > >>>> Thanks,
> > >>>> Gregor
> > >>>>
> > >>>>
> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> > wrote:
> > >>>>> Hi
> > >>>>>
> > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > getting
> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
> 38
> > >>>>> JIRAs fixed for this version and we will get a couple of more which
> > >>>>> are pending to be backported.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
Gregor are you able to cut the release for 2.21.2? Maybe we need to cut also the last release for 2.20, the 2.20.4.

Thoughts?

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino <[hidden email]> wrote:





They seem to be sporadic errors, because between 18 and 19 there weren't changes to the code base. Lets keep an eye on this job.

Thanks Onder.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:





Hi,

We have build failing on 2.22.x branch in the last two builds.

https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/

https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/

Fyi.


On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
wrote:

> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> blocking the release.
> But we still find a way to address the cached bean issue, as the bean could
> be changed dynamically.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> wrote:
>
> > Hi
> >
> > I could not find a better solution so we reverted, but kept a similar
> > unit test with a regular bean (not impl processor).
> >
> > I think the branch is potentially ready for a release.
> >
> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > wrote:
> > > Hi
> > >
> > > I am taking a look and working on either an improved fix or going to
> > revert.
> > > The issue is that the bean in use is a bit "wrong" as it implements
> > > Processor which you should not really do.
> > >
> > >
> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > <[hidden email]> wrote:
> > >> I vote for reverting it for the moment and move to the next minor
> > release.
> > >>
> > >> --
> > >> Andrea Cosentino
> > >> ----------------------------------
> > >> Apache Camel PMC Chair
> > >> Apache Karaf Committer
> > >> Apache Servicemix PMC Member
> > >> Email: [hidden email]
> > >> Twitter: @oscerd2
> > >> Github: oscerd
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > [hidden email]> wrote:
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Hi
> > >>
> > >> We need to hold the release until we get this either reverted or find
> > >> out why it causes some existing unit tests to fail
> > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > >>
> > >>
> > >>
> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > >> <[hidden email]> wrote:
> > >>> Hi,
> > >>>
> > >>> Unfortunately I was not able to cut the release due to the following
> > >>> problems with the Git repository when trying to push changes:
> > >>>
> > >>> remote: This repository has been locked due to synchronization
> issues:
> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> error,
> > >>> and prevents pushes.
> > >>> remote: This could either be a benign issue, or the repositories
> could
> > >>> be out of sync.
> > >>> remote: Please contact [hidden email] to have infrastructure
> > >>> resolve the issue.
> > >>> remote:
> > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > >>> hook declined)
> > >>> error: failed to push some refs to
> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > >>>
> > >>> Did anybody experience this in the past?
> > >>>
> > >>> Thanks in advance,
> > >>> Gregor
> > >>>
> > >>>
> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > >>> <[hidden email]> wrote:
> > >>>> Sure, I can take care of the release this weekend.
> > >>>>
> > >>>> Thanks,
> > >>>> Gregor
> > >>>>
> > >>>>
> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> > wrote:
> > >>>>> Hi
> > >>>>>
> > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > getting
> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
> 38
> > >>>>> JIRAs fixed for this version and we will get a couple of more which
> > >>>>> are pending to be backported.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
Obviously, thanks for the taking care of this.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, July 13, 2018, 11:21:44 AM GMT+2, Andrea Cosentino <[hidden email]> wrote:





Gregor are you able to cut the release for 2.21.2? Maybe we need to cut also the last release for 2.20, the 2.20.4.

Thoughts?

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino <[hidden email]> wrote:





They seem to be sporadic errors, because between 18 and 19 there weren't changes to the code base. Lets keep an eye on this job.

Thanks Onder.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:





Hi,

We have build failing on 2.22.x branch in the last two builds.

https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/

https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/

Fyi.


On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
wrote:

> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> blocking the release.
> But we still find a way to address the cached bean issue, as the bean could
> be changed dynamically.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> wrote:
>
> > Hi
> >
> > I could not find a better solution so we reverted, but kept a similar
> > unit test with a regular bean (not impl processor).
> >
> > I think the branch is potentially ready for a release.
> >
> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > wrote:
> > > Hi
> > >
> > > I am taking a look and working on either an improved fix or going to
> > revert.
> > > The issue is that the bean in use is a bit "wrong" as it implements
> > > Processor which you should not really do.
> > >
> > >
> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > <[hidden email]> wrote:
> > >> I vote for reverting it for the moment and move to the next minor
> > release.
> > >>
> > >> --
> > >> Andrea Cosentino
> > >> ----------------------------------
> > >> Apache Camel PMC Chair
> > >> Apache Karaf Committer
> > >> Apache Servicemix PMC Member
> > >> Email: [hidden email]
> > >> Twitter: @oscerd2
> > >> Github: oscerd
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > [hidden email]> wrote:
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Hi
> > >>
> > >> We need to hold the release until we get this either reverted or find
> > >> out why it causes some existing unit tests to fail
> > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > >>
> > >>
> > >>
> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > >> <[hidden email]> wrote:
> > >>> Hi,
> > >>>
> > >>> Unfortunately I was not able to cut the release due to the following
> > >>> problems with the Git repository when trying to push changes:
> > >>>
> > >>> remote: This repository has been locked due to synchronization
> issues:
> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> error,
> > >>> and prevents pushes.
> > >>> remote: This could either be a benign issue, or the repositories
> could
> > >>> be out of sync.
> > >>> remote: Please contact [hidden email] to have infrastructure
> > >>> resolve the issue.
> > >>> remote:
> > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > >>> hook declined)
> > >>> error: failed to push some refs to
> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > >>>
> > >>> Did anybody experience this in the past?
> > >>>
> > >>> Thanks in advance,
> > >>> Gregor
> > >>>
> > >>>
> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > >>> <[hidden email]> wrote:
> > >>>> Sure, I can take care of the release this weekend.
> > >>>>
> > >>>> Thanks,
> > >>>> Gregor
> > >>>>
> > >>>>
> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
> > wrote:
> > >>>>> Hi
> > >>>>>
> > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > getting
> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
> 38
> > >>>>> JIRAs fixed for this version and we will get a couple of more which
> > >>>>> are pending to be backported.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

onders-2
Hi,

This test failure is so often. In master and 2.22.x branches.
Not sure if it is blocking for release, but a notice before release.

https://builds.apache.org/job/Camel/job/master/467/testReport/



On Fri, Jul 13, 2018 at 12:23 PM Andrea Cosentino
<[hidden email]> wrote:

> Obviously, thanks for the taking care of this.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, July 13, 2018, 11:21:44 AM GMT+2, Andrea Cosentino
> <[hidden email]> wrote:
>
>
>
>
>
> Gregor are you able to cut the release for 2.21.2? Maybe we need to cut
> also the last release for 2.20, the 2.20.4.
>
> Thoughts?
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino
> <[hidden email]> wrote:
>
>
>
>
>
> They seem to be sporadic errors, because between 18 and 19 there weren't
> changes to the code base. Lets keep an eye on this job.
>
> Thanks Onder.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <
> [hidden email]> wrote:
>
>
>
>
>
> Hi,
>
> We have build failing on 2.22.x branch in the last two builds.
>
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/
>
> Fyi.
>
>
> On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
> wrote:
>
> > I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> > blocking the release.
> > But we still find a way to address the cached bean issue, as the bean
> could
> > be changed dynamically.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> > wrote:
> >
> > > Hi
> > >
> > > I could not find a better solution so we reverted, but kept a similar
> > > unit test with a regular bean (not impl processor).
> > >
> > > I think the branch is potentially ready for a release.
> > >
> > > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > > wrote:
> > > > Hi
> > > >
> > > > I am taking a look and working on either an improved fix or going to
> > > revert.
> > > > The issue is that the bean in use is a bit "wrong" as it implements
> > > > Processor which you should not really do.
> > > >
> > > >
> > > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > > <[hidden email]> wrote:
> > > >> I vote for reverting it for the moment and move to the next minor
> > > release.
> > > >>
> > > >> --
> > > >> Andrea Cosentino
> > > >> ----------------------------------
> > > >> Apache Camel PMC Chair
> > > >> Apache Karaf Committer
> > > >> Apache Servicemix PMC Member
> > > >> Email: [hidden email]
> > > >> Twitter: @oscerd2
> > > >> Github: oscerd
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > > [hidden email]> wrote:
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Hi
> > > >>
> > > >> We need to hold the release until we get this either reverted or
> find
> > > >> out why it causes some existing unit tests to fail
> > > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > > >>
> > > >>
> > > >>
> > > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > > >> <[hidden email]> wrote:
> > > >>> Hi,
> > > >>>
> > > >>> Unfortunately I was not able to cut the release due to the
> following
> > > >>> problems with the Git repository when trying to push changes:
> > > >>>
> > > >>> remote: This repository has been locked due to synchronization
> > issues:
> > > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> > error,
> > > >>> and prevents pushes.
> > > >>> remote: This could either be a benign issue, or the repositories
> > could
> > > >>> be out of sync.
> > > >>> remote: Please contact [hidden email] to have
> infrastructure
> > > >>> resolve the issue.
> > > >>> remote:
> > > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > > >>> hook declined)
> > > >>> error: failed to push some refs to
> > > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > > >>>
> > > >>> Did anybody experience this in the past?
> > > >>>
> > > >>> Thanks in advance,
> > > >>> Gregor
> > > >>>
> > > >>>
> > > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > > >>> <[hidden email]> wrote:
> > > >>>> Sure, I can take care of the release this weekend.
> > > >>>>
> > > >>>> Thanks,
> > > >>>> Gregor
> > > >>>>
> > > >>>>
> > > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <
> [hidden email]>
> > > wrote:
> > > >>>>> Hi
> > > >>>>>
> > > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > > getting
> > > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There
> are
> > 38
> > > >>>>> JIRAs fixed for this version and we will get a couple of more
> which
> > > >>>>> are pending to be backported.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> 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
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Andrea Cosentino-2
We are going to release 2.21.x so it shouldn't be a blocker.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, July 13, 2018, 2:38:40 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:





Hi,

This test failure is so often. In master and 2.22.x branches.
Not sure if it is blocking for release, but a notice before release.

https://builds.apache.org/job/Camel/job/master/467/testReport/



On Fri, Jul 13, 2018 at 12:23 PM Andrea Cosentino
<[hidden email]> wrote:

> Obviously, thanks for the taking care of this.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, July 13, 2018, 11:21:44 AM GMT+2, Andrea Cosentino
> <[hidden email]> wrote:
>
>
>
>
>
> Gregor are you able to cut the release for 2.21.2? Maybe we need to cut
> also the last release for 2.20, the 2.20.4.
>
> Thoughts?
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino
> <[hidden email]> wrote:
>
>
>
>
>
> They seem to be sporadic errors, because between 18 and 19 there weren't
> changes to the code base. Lets keep an eye on this job.
>
> Thanks Onder.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <
> [hidden email]> wrote:
>
>
>
>
>
> Hi,
>
> We have build failing on 2.22.x branch in the last two builds.
>
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/
>
> Fyi.
>
>
> On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
> wrote:
>
> > I'm sorry for the regression issue.  +1 for reverting the patch to avoid
> > blocking the release.
> > But we still find a way to address the cached bean issue, as the bean
> could
> > be changed dynamically.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> > wrote:
> >
> > > Hi
> > >
> > > I could not find a better solution so we reverted, but kept a similar
> > > unit test with a regular bean (not impl processor).
> > >
> > > I think the branch is potentially ready for a release.
> > >
> > > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
> > > wrote:
> > > > Hi
> > > >
> > > > I am taking a look and working on either an improved fix or going to
> > > revert.
> > > > The issue is that the bean in use is a bit "wrong" as it implements
> > > > Processor which you should not really do.
> > > >
> > > >
> > > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > > <[hidden email]> wrote:
> > > >> I vote for reverting it for the moment and move to the next minor
> > > release.
> > > >>
> > > >> --
> > > >> Andrea Cosentino
> > > >> ----------------------------------
> > > >> Apache Camel PMC Chair
> > > >> Apache Karaf Committer
> > > >> Apache Servicemix PMC Member
> > > >> Email: [hidden email]
> > > >> Twitter: @oscerd2
> > > >> Github: oscerd
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > > [hidden email]> wrote:
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Hi
> > > >>
> > > >> We need to hold the release until we get this either reverted or
> find
> > > >> out why it causes some existing unit tests to fail
> > > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > > >>
> > > >>
> > > >>
> > > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > > >> <[hidden email]> wrote:
> > > >>> Hi,
> > > >>>
> > > >>> Unfortunately I was not able to cut the release due to the
> following
> > > >>> problems with the Git repository when trying to push changes:
> > > >>>
> > > >>> remote: This repository has been locked due to synchronization
> > issues:
> > > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> > error,
> > > >>> and prevents pushes.
> > > >>> remote: This could either be a benign issue, or the repositories
> > could
> > > >>> be out of sync.
> > > >>> remote: Please contact [hidden email] to have
> infrastructure
> > > >>> resolve the issue.
> > > >>> remote:
> > > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
> > > >>> hook declined)
> > > >>> error: failed to push some refs to
> > > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > > >>>
> > > >>> Did anybody experience this in the past?
> > > >>>
> > > >>> Thanks in advance,
> > > >>> Gregor
> > > >>>
> > > >>>
> > > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > > >>> <[hidden email]> wrote:
> > > >>>> Sure, I can take care of the release this weekend.
> > > >>>>
> > > >>>> Thanks,
> > > >>>> Gregor
> > > >>>>
> > > >>>>
> > > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <
> [hidden email]>
> > > wrote:
> > > >>>>> Hi
> > > >>>>>
> > > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > > getting
> > > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There
> are
> > 38
> > > >>>>> JIRAs fixed for this version and we will get a couple of more
> which
> > > >>>>> are pending to be backported.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> 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
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

onders-2
Cool.

I thought this was backported.


https://issues.apache.org/jira/browse/CAMEL-12584




On Fri, 13 Jul 2018 at 15:41, Andrea Cosentino
<[hidden email]> wrote:

> We are going to release 2.21.x so it shouldn't be a blocker.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, July 13, 2018, 2:38:40 PM GMT+2, Onder SEZGIN <
> [hidden email]> wrote:
>
>
>
>
>
> Hi,
>
> This test failure is so often. In master and 2.22.x branches.
> Not sure if it is blocking for release, but a notice before release.
>
> https://builds.apache.org/job/Camel/job/master/467/testReport/
>
>
>
> On Fri, Jul 13, 2018 at 12:23 PM Andrea Cosentino
> <[hidden email]> wrote:
>
> > Obviously, thanks for the taking care of this.
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, July 13, 2018, 11:21:44 AM GMT+2, Andrea Cosentino
> > <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > Gregor are you able to cut the release for 2.21.2? Maybe we need to cut
> > also the last release for 2.20, the 2.20.4.
> >
> > Thoughts?
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino
> > <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > They seem to be sporadic errors, because between 18 and 19 there weren't
> > changes to the code base. Lets keep an eye on this job.
> >
> > Thanks Onder.
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <
> > [hidden email]> wrote:
> >
> >
> >
> >
> >
> > Hi,
> >
> > We have build failing on 2.22.x branch in the last two builds.
> >
> >
> >
> https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/
> >
> > https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/
> >
> > Fyi.
> >
> >
> > On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
> > wrote:
> >
> > > I'm sorry for the regression issue.  +1 for reverting the patch to
> avoid
> > > blocking the release.
> > > But we still find a way to address the cached bean issue, as the bean
> > could
> > > be changed dynamically.
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > I could not find a better solution so we reverted, but kept a similar
> > > > unit test with a regular bean (not impl processor).
> > > >
> > > > I think the branch is potentially ready for a release.
> > > >
> > > > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]
> >
> > > > wrote:
> > > > > Hi
> > > > >
> > > > > I am taking a look and working on either an improved fix or going
> to
> > > > revert.
> > > > > The issue is that the bean in use is a bit "wrong" as it implements
> > > > > Processor which you should not really do.
> > > > >
> > > > >
> > > > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
> > > > > <[hidden email]> wrote:
> > > > >> I vote for reverting it for the moment and move to the next minor
> > > > release.
> > > > >>
> > > > >> --
> > > > >> Andrea Cosentino
> > > > >> ----------------------------------
> > > > >> Apache Camel PMC Chair
> > > > >> Apache Karaf Committer
> > > > >> Apache Servicemix PMC Member
> > > > >> Email: [hidden email]
> > > > >> Twitter: @oscerd2
> > > > >> Github: oscerd
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
> > > > [hidden email]> wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> Hi
> > > > >>
> > > > >> We need to hold the release until we get this either reverted or
> > find
> > > > >> out why it causes some existing unit tests to fail
> > > > >> https://issues.apache.org/jira/browse/CAMEL-12610
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
> > > > >> <[hidden email]> wrote:
> > > > >>> Hi,
> > > > >>>
> > > > >>> Unfortunately I was not able to cut the release due to the
> > following
> > > > >>> problems with the Git repository when trying to push changes:
> > > > >>>
> > > > >>> remote: This repository has been locked due to synchronization
> > > issues:
> > > > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
> > > error,
> > > > >>> and prevents pushes.
> > > > >>> remote: This could either be a benign issue, or the repositories
> > > could
> > > > >>> be out of sync.
> > > > >>> remote: Please contact [hidden email] to have
> > infrastructure
> > > > >>> resolve the issue.
> > > > >>> remote:
> > > > >>> To https://gitbox.apache.org/repos/asf/camel.git
> > > > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2
> (pre-receive
> > > > >>> hook declined)
> > > > >>> error: failed to push some refs to
> > > > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
> > > > >>>
> > > > >>> Did anybody experience this in the past?
> > > > >>>
> > > > >>> Thanks in advance,
> > > > >>> Gregor
> > > > >>>
> > > > >>>
> > > > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
> > > > >>> <[hidden email]> wrote:
> > > > >>>> Sure, I can take care of the release this weekend.
> > > > >>>>
> > > > >>>> Thanks,
> > > > >>>> Gregor
> > > > >>>>
> > > > >>>>
> > > > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <
> > [hidden email]>
> > > > wrote:
> > > > >>>>> Hi
> > > > >>>>>
> > > > >>>>> After the Camel 2.22.0 release, then I think we should work on
> > > > getting
> > > > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There
> > are
> > > 38
> > > > >>>>> JIRAs fixed for this version and we will get a couple of more
> > which
> > > > >>>>> are pending to be backported.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> 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
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Gregor Zurowski-2
In reply to this post by Andrea Cosentino-2
Hi,

I will now proceed with re-cutting the 2.21.2 release. And yes, I can
also look into the 2.20.4 release if everybody agrees.

Thanks,
Gregor


On Fri, Jul 13, 2018 at 11:21 AM, Andrea Cosentino
<[hidden email]> wrote:

> Gregor are you able to cut the release for 2.21.2? Maybe we need to cut also the last release for 2.20, the 2.20.4.
>
> Thoughts?
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino <[hidden email]> wrote:
>
>
>
>
>
> They seem to be sporadic errors, because between 18 and 19 there weren't changes to the code base. Lets keep an eye on this job.
>
> Thanks Onder.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:
>
>
>
>
>
> Hi,
>
> We have build failing on 2.22.x branch in the last two builds.
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/
>
> https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/
>
> Fyi.
>
>
> On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
> wrote:
>
>> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
>> blocking the release.
>> But we still find a way to address the cached bean issue, as the bean could
>> be changed dynamically.
>>
>>
>> Willem Jiang
>>
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
>> wrote:
>>
>> > Hi
>> >
>> > I could not find a better solution so we reverted, but kept a similar
>> > unit test with a regular bean (not impl processor).
>> >
>> > I think the branch is potentially ready for a release.
>> >
>> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
>> > wrote:
>> > > Hi
>> > >
>> > > I am taking a look and working on either an improved fix or going to
>> > revert.
>> > > The issue is that the bean in use is a bit "wrong" as it implements
>> > > Processor which you should not really do.
>> > >
>> > >
>> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
>> > > <[hidden email]> wrote:
>> > >> I vote for reverting it for the moment and move to the next minor
>> > release.
>> > >>
>> > >> --
>> > >> Andrea Cosentino
>> > >> ----------------------------------
>> > >> Apache Camel PMC Chair
>> > >> Apache Karaf Committer
>> > >> Apache Servicemix PMC Member
>> > >> Email: [hidden email]
>> > >> Twitter: @oscerd2
>> > >> Github: oscerd
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
>> > [hidden email]> wrote:
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> Hi
>> > >>
>> > >> We need to hold the release until we get this either reverted or find
>> > >> out why it causes some existing unit tests to fail
>> > >> https://issues.apache.org/jira/browse/CAMEL-12610
>> > >>
>> > >>
>> > >>
>> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
>> > >> <[hidden email]> wrote:
>> > >>> Hi,
>> > >>>
>> > >>> Unfortunately I was not able to cut the release due to the following
>> > >>> problems with the Git repository when trying to push changes:
>> > >>>
>> > >>> remote: This repository has been locked due to synchronization
>> issues:
>> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
>> error,
>> > >>> and prevents pushes.
>> > >>> remote: This could either be a benign issue, or the repositories
>> could
>> > >>> be out of sync.
>> > >>> remote: Please contact [hidden email] to have infrastructure
>> > >>> resolve the issue.
>> > >>> remote:
>> > >>> To https://gitbox.apache.org/repos/asf/camel.git
>> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
>> > >>> hook declined)
>> > >>> error: failed to push some refs to
>> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
>> > >>>
>> > >>> Did anybody experience this in the past?
>> > >>>
>> > >>> Thanks in advance,
>> > >>> Gregor
>> > >>>
>> > >>>
>> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
>> > >>> <[hidden email]> wrote:
>> > >>>> Sure, I can take care of the release this weekend.
>> > >>>>
>> > >>>> Thanks,
>> > >>>> Gregor
>> > >>>>
>> > >>>>
>> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
>> > wrote:
>> > >>>>> Hi
>> > >>>>>
>> > >>>>> After the Camel 2.22.0 release, then I think we should work on
>> > getting
>> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
>> 38
>> > >>>>> JIRAs fixed for this version and we will get a couple of more which
>> > >>>>> are pending to be backported.
>> > >>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>> --
>> > >>>>> 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
>> >
>>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Camel 2.21.2 patch release

Claus Ibsen-2
Hi

Thanks Gregor that sounds great.

On Mon, Jul 16, 2018 at 11:40 AM, Gregor Zurowski
<[hidden email]> wrote:

> Hi,
>
> I will now proceed with re-cutting the 2.21.2 release. And yes, I can
> also look into the 2.20.4 release if everybody agrees.
>
> Thanks,
> Gregor
>
>
> On Fri, Jul 13, 2018 at 11:21 AM, Andrea Cosentino
> <[hidden email]> wrote:
>> Gregor are you able to cut the release for 2.21.2? Maybe we need to cut also the last release for 2.20, the 2.20.4.
>>
>> Thoughts?
>>
>> --
>> Andrea Cosentino
>> ----------------------------------
>> Apache Camel PMC Chair
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: [hidden email]
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Thursday, July 12, 2018, 12:19:48 PM GMT+2, Andrea Cosentino <[hidden email]> wrote:
>>
>>
>>
>>
>>
>> They seem to be sporadic errors, because between 18 and 19 there weren't changes to the code base. Lets keep an eye on this job.
>>
>> Thanks Onder.
>>
>> --
>> Andrea Cosentino
>> ----------------------------------
>> Apache Camel PMC Chair
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: [hidden email]
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Thursday, July 12, 2018, 12:09:35 PM GMT+2, Onder SEZGIN <[hidden email]> wrote:
>>
>>
>>
>>
>>
>> Hi,
>>
>> We have build failing on 2.22.x branch in the last two builds.
>>
>> https://builds.apache.org/job/Camel/job/camel-2.22.x/lastCompletedBuild/testReport/
>>
>> https://builds.apache.org/job/Camel/job/camel-2.22.x/18/testReport/
>>
>> Fyi.
>>
>>
>> On Tue, Jul 10, 2018 at 12:58 PM Willem Jiang <[hidden email]>
>> wrote:
>>
>>> I'm sorry for the regression issue.  +1 for reverting the patch to avoid
>>> blocking the release.
>>> But we still find a way to address the cached bean issue, as the bean could
>>> be changed dynamically.
>>>
>>>
>>> Willem Jiang
>>>
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>> On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <[hidden email]>
>>> wrote:
>>>
>>> > Hi
>>> >
>>> > I could not find a better solution so we reverted, but kept a similar
>>> > unit test with a regular bean (not impl processor).
>>> >
>>> > I think the branch is potentially ready for a release.
>>> >
>>> > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <[hidden email]>
>>> > wrote:
>>> > > Hi
>>> > >
>>> > > I am taking a look and working on either an improved fix or going to
>>> > revert.
>>> > > The issue is that the bean in use is a bit "wrong" as it implements
>>> > > Processor which you should not really do.
>>> > >
>>> > >
>>> > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino
>>> > > <[hidden email]> wrote:
>>> > >> I vote for reverting it for the moment and move to the next minor
>>> > release.
>>> > >>
>>> > >> --
>>> > >> Andrea Cosentino
>>> > >> ----------------------------------
>>> > >> Apache Camel PMC Chair
>>> > >> Apache Karaf Committer
>>> > >> Apache Servicemix PMC Member
>>> > >> Email: [hidden email]
>>> > >> Twitter: @oscerd2
>>> > >> Github: oscerd
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen <
>>> > [hidden email]> wrote:
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >> Hi
>>> > >>
>>> > >> We need to hold the release until we get this either reverted or find
>>> > >> out why it causes some existing unit tests to fail
>>> > >> https://issues.apache.org/jira/browse/CAMEL-12610
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski
>>> > >> <[hidden email]> wrote:
>>> > >>> Hi,
>>> > >>>
>>> > >>> Unfortunately I was not able to cut the release due to the following
>>> > >>> problems with the Git repository when trying to push changes:
>>> > >>>
>>> > >>> remote: This repository has been locked due to synchronization
>>> issues:
>>> > >>> remote:  - /x1/gitbox/broken/camel.txt exists due to a previous
>>> error,
>>> > >>> and prevents pushes.
>>> > >>> remote: This could either be a benign issue, or the repositories
>>> could
>>> > >>> be out of sync.
>>> > >>> remote: Please contact [hidden email] to have infrastructure
>>> > >>> resolve the issue.
>>> > >>> remote:
>>> > >>> To https://gitbox.apache.org/repos/asf/camel.git
>>> > >>>  ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive
>>> > >>> hook declined)
>>> > >>> error: failed to push some refs to
>>> > >>> 'https://gitbox.apache.org/repos/asf/camel.git'
>>> > >>>
>>> > >>> Did anybody experience this in the past?
>>> > >>>
>>> > >>> Thanks in advance,
>>> > >>> Gregor
>>> > >>>
>>> > >>>
>>> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski
>>> > >>> <[hidden email]> wrote:
>>> > >>>> Sure, I can take care of the release this weekend.
>>> > >>>>
>>> > >>>> Thanks,
>>> > >>>> Gregor
>>> > >>>>
>>> > >>>>
>>> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <[hidden email]>
>>> > wrote:
>>> > >>>>> Hi
>>> > >>>>>
>>> > >>>>> After the Camel 2.22.0 release, then I think we should work on
>>> > getting
>>> > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are
>>> 38
>>> > >>>>> JIRAs fixed for this version and we will get a couple of more which
>>> > >>>>> are pending to be backported.
>>> > >>>>>
>>> > >>>>>
>>> > >>>>>
>>> > >>>>> --
>>> > >>>>> 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