Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of eli@cloudera.com designates
 209.85.215.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C9E7240C.19FDC%sureshms@yahoo-inc.com>
References: <BANLkTikU1NmH0NM+Gu95PU9cWsHNQ_VbBg@mail.gmail.com>
	<C9E7240C.19FDC%sureshms@yahoo-inc.com>
Date: Wed, 4 May 2011 15:51:26 -0700
Message-ID: <BANLkTi=B+cc_677HC1wRnpcY73zuF8qekg@mail.gmail.com>
Subject: Re: [VOTE] Release candidate 0.20.203.0-rc1
From: Eli Collins <eli@cloudera.com>
To: general@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

> Your -1 vote essentially blocks the changes that are already available in
> CDH to be available from Apache open source!

As Eric mentioned, this thread is about an Apache release, not CDH.

My -1 vote does not block these changes from being released via
Apache. You can not veto a release. Releases are lazy majority, the
release is only blocked if there are more -1 votes than +1 votes.

If these changes are contributed on jira, discussed and reviewed, and
committed to trunk I'm happy to support the release.  There's a big
difference between asking that a release respect the Apache community
process and blocking it. If you want to get the release out how about
contributing the work via the normal means so the community can review
it like we review all other code changes.

Thanks,
Eli