Hi Hadrian Do you have a minute to comment when you have time to do a 2.0m2 release? If you do not have the time, do you think I (or Jonathan) have sufficient privileges to try doing the release?
Its important that we get a 2.0m2 out of the door now. We have approx 200 tickets fixed since 2.0m1 and there have been major work done, so its important to give the community time to test drive it before we start finalizing and doing a RC cut. On Mon, May 25, 2009 at 9:38 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, May 25, 2009 at 9:32 AM, S. Ali Tokmen > <savas-ali.tok...@bull.net> wrote: >> Hello >> >> Does this mean that CAMEL 2.0-M2 will be based on revision 777408? > I think Hadrian will do the 2.0m2 release at any day when he has time. > And usually its based on the trunk revision at the time. > > So if he does it tomorrow then the commits of this day is usually in > the 2.0m2 release also. > > Hadrian your comments? > > >> >> Thanks >> >> S. Ali Tokmen >> savas-ali.tok...@bull.net >> >> Office: +33 4 76 29 76 19 >> GSM: +33 66 43 00 555 >> >> Bull, Architect of an Open World TM >> http://www.bull.com >> >> >> >> Willem Jiang a écrit : >>> >>> Hi Hadrain, >>> >>> I just change the trunk code to use camel internal maven repository to >>> look up the internal version of spring javaconfig[1]. >>> Now we should ready for the Camel 2.0-m2 release :) >>> >>> [1]https://issues.apache.org/activemq/browse/CAMEL-1635 >>> >>> Cheers, >>> >>> Willem >>> >>> Willem Jiang wrote: >>> >>>> >>>> Hi Hadrain >>>> >>>> I fixed the build by reverting the spring javaconfig to 1.0-SNAPSHOT. >>>> I will setup an internal maven repository in the camel svn repository to >>>> hold the latest spring javaconfig. In this way , we can get control of >>>> Camel releasing. >>>> >>>> Cheers, >>>> >>>> Willem >>>> >>>> Hadrian Zbarcea wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> I am ready to issue the 2.0-M2 release, the only problem is that after >>>>> going back to the 1.0 M4 release of javaconfig the tests fail and didn't >>>>> have the time to figure out why. The problem is related to endpoints >>>>> not being injected, afaict. >>>>> >>>>> I will be flying to Europe now and won't be online probably until >>>>> Sat/Sun when I'll build the kit. If anybody can fix those tests that'd >>>>> be great, if not I'll disable the tests and proceed with the release, as >>>>> javaconfig is experimental for the M2 release. >>>>> >>>>> If anybody disagrees please shout, or even better fix the tests. >>>>> >>>>> Cheers >>>>> Hadrian >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
