On Sat, Jan 4, 2014 at 11:21 PM, Christian Müller
<christian.muel...@gmail.com> wrote:
> I think Camel 2.11.3 is overdue. Should I take over?
>

Yeah that would be good, so we can get that release out of the door.

And we could also do a 2.12.3 release as well, maybe towards the end
of this month.


> Best,
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Wed, Nov 27, 2013 at 6:04 AM, Hadrian Zbarcea <hzbar...@gmail.com> wrote:
>
>> Done. Next is camel-2.11.3 this week.
>> Hadrian
>>
>>
>>
>> On 11/22/2013 10:44 PM, Hadrian Zbarcea wrote:
>>
>>> The release is done, but for some reason the apache repo doesn't let me
>>> close the staging repo:
>>>
>>> The server did not close the staging repository.
>>> Nexus returned an error: ERROR 502: Proxy Error
>>>
>>> I'll try again in the morning and take it with infra if necessary. I
>>> will start the vote as soon as the staging repo is closed.
>>>
>>> Hadrian
>>>
>>>
>>> On 11/11/2013 01:33 PM, Claus Ibsen wrote:
>>>
>>>> Hi
>>>>
>>>> I think we should cut a new 2.12.2 release later this month. We have
>>>> so far 115 jira's resolved.
>>>>
>>>> Any thoughts?
>>>>
>>>>
>>>>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io

Reply via email to