Get well soon!

Best,
Christian


On Tue, Oct 14, 2014 at 10:27 PM, Daniel Kulp <dk...@apache.org> wrote:

>
> There are new releases of CXF out that do fix some security issues….  I’m
> too sick to test/commit right now, but it might be good to give it a try.
>
> Dan
>
>
>
> On Oct 14, 2014, at 3:39 PM, Christian Müller <christian.muel...@gmail.com>
> wrote:
>
> > I could do the 2.12.5 release (last planned patch release of the 2.12.x
> > branch).
> > If nobody has an important ticket which should be included, I will start
> > the release in 24 hours.
> >
> > Best,
> > Christian
> >
> >
> > On Tue, Oct 14, 2014 at 3:21 AM, Willem Jiang <willem.ji...@gmail.com>
> > wrote:
> >
> >> Yeah, I totally agree with that.
> >> As my schedule is occupied this two weeks, the release will be scheduled
> >> at the last week of this month.
> >> If other release managers have time before that, any help will be
> >> appreciated.
> >>
> >> --
> >> Willem Jiang
> >>
> >> Red Hat, Inc.
> >> Web: http://www.redhat.com
> >> Blog: http://willemjiang.blogspot.com (English)
> >> http://jnn.iteye.com (Chinese)
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >>
> >>
> >> On October 1, 2014 at 2:45:07 PM, Claus Ibsen (claus.ib...@gmail.com)
> >> wrote:
> >>> Hi
> >>>
> >>> Now that we have 2.14.0 out of the door, I think its time we do a
> >>> round of patch releases.
> >>>
> >>> Camel 2.12.5 would be the last planned patch release of the 2.12.x
> >> branch.
> >>> Camel 2.13.3 is a patch release.
> >>>
> >>> Its 3 months ago since we last release patch releases for these two
> >> branches.
> >>>
> >>> 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
> >>> hawtio: http://hawt.io/
> >>> fabric8: http://fabric8.io/
> >>>
> >>
> >>
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Reply via email to