Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E44CF3522 for ; Thu, 5 May 2011 01:57:15 +0000 (UTC) Received: (qmail 48793 invoked by uid 500); 5 May 2011 01:57:14 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 48731 invoked by uid 500); 5 May 2011 01:57:14 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 48723 invoked by uid 99); 5 May 2011 01:57:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 01:57:14 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.97.132.119] (HELO homiemail-a70.g.dreamhost.com) (208.97.132.119) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 01:57:06 +0000 Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id 5BEDF768061 for ; Wed, 4 May 2011 18:56:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; q=dns; s= gbiv.com; b=o8K7ro00lw7lm14JUSdbP+RBQ6vxxpFgzaYdbIwZqVq6y1vS2KUA 9327QkUQeYydfZLvRCZtr3mg3iSZNP117APxZcKh9uUoak9Vh2OgAD9vM8Ejw3Dd L8Rw06iUayYScVwB/FnsTITXvLZ0it5F8hgqDIqj/wuE2R9F9cDJKpI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=VoGFmmPH0I6KQnbDbYMrb5glrgw=; b=BjiNW3u3aWHiWJKLNEZImTlO+MGl 8sfKwSpyynb2u05ko2PVKaFaFOHA3ZpdfO7xzQTYm/zhChyx3gFzbjKpOBXszaGa 0HGSe2e3d6q0P8EX3oqtZm6GI8cwIKoEVywYJimjJ2LPmU5xa7kwhY7cWKfcR6ws dV5iDiAVEtTJCH4= Received: from [10.134.89.86] (unknown [75.103.10.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPSA id 4252676805C for ; Wed, 4 May 2011 18:56:45 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [VOTE] Release candidate 0.20.203.0-rc1 From: "Roy T. Fielding" In-Reply-To: Date: Wed, 4 May 2011 18:56:44 -0700 Content-Transfer-Encoding: 7bit Message-Id: <79A1AED5-9005-4F58-BFDB-F7394CB2A69C@gbiv.com> References: <321761.51699.qm@web65903.mail.ac4.yahoo.com> To: general@hadoop.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org On May 4, 2011, at 5:39 PM, Eli Collins wrote: > The point is that these discussion should be sorted out, ie you don't > change your development and release model on a release VOTE thread, > you change it on a DISCUSSION thread. That is no different than saying you have a right to veto a release until the issue is addressed, which you don't have. A release vote is a majority decision. If the majority decides to release, then whatever gets released will define the new norm by which policies are assumed. If not released, then I suggest collaborating more on the policies before trying to vote again. Either way, we don't hold up a vote for the sake of a policy discussion because voting is a more efficient means of discovering if the policy really matters. ....Roy