> > Today, CS uses 5.6.100 iirc - in my mind it makes sense to use the > latest and > > greatest - but I also am not maintaining the code that does the work. > Perhaps > > they will weigh in on the matter. > > Anthony, can you comment on this? The question goes back to Mike's > earlier question:
We did move XAPI version once, from 5.6 GA to 5.6.100. XAPI used RPC to communicate with XenServer, but there is not RPC timeout in XenServer side. We added some codes to make RPC client timeout configurable, and we have some other fixes. XAPI is supposed to be stable, and upgrade to latest version introduces a lot of test effort. So we are reluctant to upgrade to latest version. The reason we upgraded to 5.6.100 is, We found some fixes we did in XAPI 5.6 are already in XAPI 5.6.100, and XAPI 5.6.100 fixed some other issue we want. To be honestly, we didn't look at XAPI 6.0.* yet. And we are glad with XAPI 5.6.100. Thanks Anthony > -----Original Message----- > From: Kevin Kluge > Sent: Wednesday, May 30, 2012 4:46 PM > To: cloudstack-dev@incubator.apache.org > Cc: Anthony Xu > Subject: RE: XAPI API (aka xenserver-java) > > > I can't speak for the folks at the ASF - perhaps asking on legal@ or > filing a bug > > in Legal's Jira instance would get you a more qualified response. My > question > > on this would be - is there any reason not to release the generating > code? > > I don't see why the generating code needs to be released. CloudStack > doesn't incorporate it. Also, GPL and other tools are used all the > time in the development of ASF code... > > > Today, CS uses 5.6.100 iirc - in my mind it makes sense to use the > latest and > > greatest - but I also am not maintaining the code that does the work. > Perhaps > > they will weigh in on the matter. > > Anthony, can you comment on this? The question goes back to Mike's > earlier question: > > > > - Will we have to re-license and re-publish previously released > > > versions of the xenserverjava library? Which versions does > CloudStack > > > depend on? Would it instead be sufficient to re-license the library > in > > > the next version of XenServer? > > Mike, the community wants to get an Apache CloudStack release out > "quickly" and from what I know of XenServer product timelines they > would not qualify as "quick". So I'd request that Citrix do a release > of the XenServerJava library outside the XenServer release framework. > This could even be a re-release of whatever CloudStack is currently > using. > > -kevin
