Thanks for the suggestions. @Claus are you suggesting to wait till a GA release is available or add the component to master now and not release it till there is GA release of Infinispan?
Thanks Bilgin > As its alpha release it may have API changes on the way and whatnot. > So I think we should wait until its first GA release. > > Though the code can be committed to master at ASF as we can just avoid > release camel-infinispan. But having the code at ASF allows us to work > on it, and as well test it with OSGi / Karaf etc. > > On Wed, Jul 24, 2013 at 11:01 AM, Willem jiang <willem.ji...@gmail.com> wrote: >> I think we can wait for the Infinispan RC release before movie the component >> into Camel trunk. >> In this way, camel-infinispan component will not hold the release steps of >> Camel. >> >> Any thoughts? >> >> -- >> Willem Jiang >> >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Web: http://www.fusesource.com | http://www.redhat.com >> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) >> (English) >> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> >> >> >> >> On Wednesday, July 24, 2013 at 1:53 AM, Bilgin Ibryam wrote: >> >>> Hi guys, >>> >>> I've created a JBoss Infinispan component for Camel >>> It is here https://github.com/bibryam/camel-infinispan >>> >>> I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2 >>> >>> Do we have any policy for not adding libraries which are Alpha, when >>> would be a good time to add this component to Camel trunk? >>> >>> Cheers >>> Bilgin >> >> >> > > > > -- > 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
