On Fri, Oct 19, 2012 at 12:55 PM, Chip Childers <chip.child...@sungard.com> wrote: > Hi all, > > Following up on the OVM discussion thread [1], it appears that we > don't have a full consensus yet. In order to move forward and make a > decision as a community, I would like to formally call a vote on this > issue. > > I'm proposing that we drop support of OVM for 4.0.0-incubating. I am > NOT proposing that this drop is permanent. If someone were to decide > that this is important enough to fix / update that code, then I would > be in full support of that effort. > > IMO, we can't block a release just because of preference. So if you > vote -1 for dropping support, I would like to know how you can help > get OVM fixed (coding, testing, documenting) for the release. > > So, for the vote, please respond with one of the following: > > [ ] +1 : we should drop support of OVM from the 4.0.0-incubating release > [ ] 0 : you don't have an opinion > [ ] -1 : we should not drop support of OVM, and do the work required > to get it ready prior to a 4.0.0-incubating release > > Thanks all! > > -chip > > > [1] http://markmail.org/message/ey5zbnhdjik2m2em
So I'll vote - though I think it's largely pointless. Regardless of the vote outcome I don't think we can dictate whether OVM works or not (collection of leaderless individuals and all and this really isn't a product management question) Someone picks it up or doesn't - effectively OVM support is dead at the moment. The question to us is really whether and how long we hold off releasing while waiting to see if OVM support is picked back up. To be clear, I hate that OVM support is in its current state, I want it back, but not going to hold my breath waiting for a unicorn to come over the rainbow. (but I'd be delighted to see one :) ) +1 - Support was (apparently) dropped long ago; we should move on. --David
