Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of calebcall@me.com designates
 17.158.236.238 as permitted sender)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Subject: Re: [VOTE][ASFCS40] Drop OVM from the supported HV list for
 4.0.0-incubating release?
From: Caleb Call <calebcall@me.com>
In-reply-to: 
 <CA+96GG7uiAZt_y3rE-jNUO4efJHFZH21-vv=j+vc3Ox3pxiF5w@mail.gmail.com>
Date: Fri, 19 Oct 2012 14:22:54 -0600
Message-id: <89247D54-3D59-4B9A-9768-053209EA4571@me.com>
References: 
 <CA+96GG7uiAZt_y3rE-jNUO4efJHFZH21-vv=j+vc3Ox3pxiF5w@mail.gmail.com>
To: cloudstack-dev@incubator.apache.org

+1 not to hold up the release (with hope that it's picked up in a future release)


On Oct 19, 2012, at 10:55 AM, Chip Childers <chip.childers@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