I just upgraded my local workspace to CXF 2.7.9 which I would like to see in the next Camel versions [1]. The test suite is still running...
Afterwards I would like to give Camel 2.12.3 a "dry run"... At present, we have 8 outstanding issues for 2.12.3 [2] (my one included). Only one is classified as bug [3], but with minor priority. Any problems with moving these issues to 2.12.4? [1] https://issues.apache.org/jira/browse/CAMEL-7170 [2] https://issues.apache.org/jira/browse/CAMEL-6807?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.12.3%22%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29 [3] https://issues.apache.org/jira/browse/CAMEL-6807 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 Tue, Feb 4, 2014 at 9:39 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, Feb 3, 2014 at 5:48 PM, Jack <jrmpatw...@gmail.com> wrote: > > Hi, > > > > Can anyone tell me when either of these planned releases (2.12.3, 2.13.0) > > will be happening? > > > > Later this year :) > > Okay people is busy and there is winter vacation for some and others > have chinese new-year. > But a new batch of releases for 2.12 / 2.11 and likely 2.13 is being > discussed and released in due time. > Hopefully later this month, but surely the aim would be for releases > out in Q1 2014. > > > > We¹re affected by the memory leak in the BacklogTracer and just need to > know > > how long it will be before a fix is released. > > https://issues.apache.org/jira/browse/CAMEL-7062 > > > > You can just patch it yourself and then upgrade when there is a public > release. > > > > > Thanks, > > > > Jack > > > > > > > > -- > 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 >
