On Thu, Oct 18, 2012 at 03:00:03PM -0700, Edison Su wrote: > Nobody complains OVM doesn't work in 4.0 before, means nobody use and > test it on 4.0 branch since half year ago when we starting to work on > 4.0 release.
"Since half a year ago"? Let's be realistic. How long has the 4.0 branch been in a state that people could test it, if they're not developers? Two months? It's not half a year by a long stretch. (Remember, we're talking about users and folks deploying CloudStack, not folks who are watching git and compiling it themselves.) When 3.0 was released, upgrading from 2.2 was not supported: http://www.cloudstack.org/blog/117-cloudstack-acton-released.html So let's recap: 4.0 hasn't been in a state to test realistically for more than two months - and that's being generous. The 3.0 release was not recommended for upgrades - so 2.2 users who did have OVM support wouldn't have tried to upgrade. Shortly after, the move to Apache was announced and the open source version effectively froze at 3.0.2. It's also not like every 2.2.x user has rushed to upgrade immediately. At least one user has spoken up on cloudstack-user to voice support for OVM. I don't know how many folks don't read the lists and aren't aware of the potential for it to be dropped. Having been through this scenario before when openSUSE dropped PPC, I'm guessing we will hear from folks after the 4.0.0-incubating release actually hits the streets and the few OVM users who were hoping to upgrade can't. If nothing else, I hope this is the only time this kind of feature attrition happens without giving folks due notice to pick up the feature. -- Joe Brockmeier Twitter: @jzb http://dissociatedpress.net/
