Possible, as the OVM code is in its own separate folder, the OVM fix will not impact other code at all. We can have 4.0.x release to fix OVM.
> -----Original Message----- > From: Kelcey Damage (BBITS) [mailto:kel...@bbits.ca] > Sent: Wednesday, October 17, 2012 11:28 AM > To: cloudstack-dev@incubator.apache.org > Cc: cloudstack-us...@incubator.apache.org > Subject: RE: Drop OVM in 4.0? > > Could OVM be made a hot fix post 4.0 release, but not held to the > official 4.1? > > KELCEY DAMAGE > Infrastructure Systems Architect > www.backbonetechnology.com > ----------------------------------------------------------------------- > -- > kel...@bbits.ca > > address: 55 East 7th Ave, Vancouver, BC, V5T 1M4 > tel: +1 604 713 8560 ext:114 > fax: +1 604 605 0964 > skype: kelcey.damage > > > > -----Original Message----- > From: Edison Su [mailto:edison...@citrix.com] > Sent: Wednesday, October 17, 2012 11:26 AM > To: cloudstack-dev@incubator.apache.org > Cc: cloudstack-us...@incubator.apache.org > Subject: Drop OVM in 4.0? > > Hi All, > Due to the bug http://bugs.cloudstack.org/browse/CS-16488 and the > license issue(some files related to OVM are removed on 4.0 > branch(https://git-wip-us.apache.org/repos/asf?p=incubator- > cloudstack.git;a=commit;h=7f8a1aabbf9b6764780e0c2ad870009c5555c2d4)), > OVM is not supported on 4.0 branch, currently. > It will take a while(maybe one or two weeks to get OVM back to work), > will we wait for OVM before releasing 4.0, or move OVM into 4.1 release?
