Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ9DK3zYdv6AjX51c-rT8VRRsHM8QyZRe8wT19+0rbbS8U_gZA@mail.gmail.com>
References: 
 <CAJ9DK3yJUfUsRHHvSWXQe+s0d_r4jewn96KddXgYRvDk8ARexQ@mail.gmail.com>
 <CAGB5yNnPjK90hWxUizTEDwRD5U=oVhvM1iOAf=bk-UsKUUDc1Q@mail.gmail.com>
 <CAJ9DK3zYdv6AjX51c-rT8VRRsHM8QyZRe8wT19+0rbbS8U_gZA@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 19 Jan 2013 16:16:32 +0100
Message-ID: 
 <CAGB5yN=hAALv5Bg8n9iQEXSb7ti05i9vC_hOt6kkeM7UGvdaYA@mail.gmail.com>
Subject: Re: [Discuss] Apache Karaf 2.3.1 RC in two weeks time?
To: dev@karaf.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Jan 19, 2013 at 3:08 PM, Jamie G. <jamie.goodyear@gmail.com> wrote:
> Hi Claus,
>
> The RC run starts this week. We gave ourselves 2 weeks to get current
> inflight issues resolved or scheduled for another version.
>
> Cheers,
> Jamie
>

Thanks Jamie for the status update.


> On Sat, Jan 19, 2013 at 2:34 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>> Hi
>>
>> Any update on a Karaf 2.3.1 release?
>>
>> Its 11 days since you you wrote this mail. It would be great to get
>> this release out to the community soon.
>> Its 3 months since the 2.3.0 release and when using a new minor
>> release then as a community user,
>> would love to see sooner patch releases to iron out the glitches and
>> bugs that it has. So running on a more
>> stable server is possible.
>>
>> It would be good for the next minor/major release that the 1st patch
>> release comes out quicker.
>>
>>
>> On Tue, Jan 8, 2013 at 6:16 PM, Jamie G. <jamie.goodyear@gmail.com> wrote:
>>> Hi All,
>>>
>>> First off, happy new year to the community, secondly, I'd like to
>>> schedule Apache Karaf 2.3.1 RC for two weeks time from now.
>>>
>>> We have a lot of resolved issues at the moment, and several issues in
>>> progress. I think 2 weeks should be sufficient to close up these
>>> in-flight issues, then prep for the RC build.
>>>
>>> Are there any issues that anyone sees as a show stopper that would
>>> require a longer development window?
>>>
>>> Cheers,
>>> Jamie
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen