Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D0B911203 for ; Sat, 21 Jun 2014 09:20:51 +0000 (UTC) Received: (qmail 81570 invoked by uid 500); 21 Jun 2014 09:20:49 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 81437 invoked by uid 500); 21 Jun 2014 09:20:49 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 80120 invoked by uid 99); 21 Jun 2014 09:20:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jun 2014 09:20:46 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of uma.gangumalla@intel.com designates 134.134.136.24 as permitted sender) Received: from [134.134.136.24] (HELO mga09.intel.com) (134.134.136.24) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jun 2014 09:20:40 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 21 Jun 2014 02:14:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,519,1400050800"; d="scan'208";a="531935850" Received: from fmsmsx107.amr.corp.intel.com ([10.19.9.54]) by orsmga001.jf.intel.com with ESMTP; 21 Jun 2014 02:19:54 -0700 Received: from bgsmsx151.gar.corp.intel.com (10.224.48.42) by FMSMSX107.amr.corp.intel.com (10.19.9.54) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sat, 21 Jun 2014 02:19:54 -0700 Received: from bgsmsx102.gar.corp.intel.com ([169.254.2.210]) by BGSMSX151.gar.corp.intel.com ([169.254.3.126]) with mapi id 14.03.0123.003; Sat, 21 Jun 2014 14:49:51 +0530 From: "Gangumalla, Uma" To: "common-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" Subject: RE: [DISCUSS] Change by-laws on release votes: 5 days instead of 7 Thread-Topic: [DISCUSS] Change by-laws on release votes: 5 days instead of 7 Thread-Index: AQHPjRVhoLJ2KiqYdEaAGI882NR6Npt7MV4A Date: Sat, 21 Jun 2014 09:19:51 +0000 Message-ID: <6A0439AD4731794E8EB53669FA76B11B0F3DF4F4@BGSMSX102.gar.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org How about proposing vote for 5days and give chance to RM for extending vote= for 2more days( total to 7days) if the rc did not receive enough vote with= in 5days? If a rc received enough votes in 5days, RM can close vote. I can see an advantage of 7days voting is, that will cover all the week and= weekend days. So, if someone wants to test on weekend time(due to the week= day schedules), that will give chance to them.=20 Regards, Uma -----Original Message----- From: Arun C Murthy [mailto:acm@hortonworks.com]=20 Sent: Saturday, June 21, 2014 11:25 AM To: hdfs-dev@hadoop.apache.org; common-dev@hadoop.apache.org; yarn-dev@hado= op.apache.org; mapreduce-dev@hadoop.apache.org Subject: [DISCUSS] Change by-laws on release votes: 5 days instead of 7 Folks, I'd like to propose we change our by-laws to reduce our voting periods on = new releases from 7 days to 5. Currently, it just takes too long to turn around releases; particularly if= we have critical security fixes etc. Thoughts? thanks, Arun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to= which it is addressed and may contain information that is confidential, pr= ivileged and exempt from disclosure under applicable law. If the reader of = this message is not the intended recipient, you are hereby notified that an= y printing, copying, dissemination, distribution, disclosure or forwarding = of this communication is strictly prohibited. If you have received this com= munication in error, please contact the sender immediately and delete it fr= om your system. Thank You.