From hdfs-dev-return-1453-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org Fri Aug 20 00:33:13 2010 Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 8210 invoked from network); 20 Aug 2010 00:33:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Aug 2010 00:33:12 -0000 Received: (qmail 21981 invoked by uid 500); 20 Aug 2010 00:33:12 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 21899 invoked by uid 500); 20 Aug 2010 00:33:11 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 21891 invoked by uid 99); 20 Aug 2010 00:33:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Aug 2010 00:33:11 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.237.123] (HELO n10.bullet.re3.yahoo.com) (68.142.237.123) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 20 Aug 2010 00:33:04 +0000 Received: from [68.142.237.87] by n10.bullet.re3.yahoo.com with NNFMP; 20 Aug 2010 00:32:43 -0000 Received: from [66.196.97.143] by t3.bullet.re3.yahoo.com with NNFMP; 20 Aug 2010 00:32:43 -0000 Received: from [127.0.0.1] by omp201.mail.re3.yahoo.com with NNFMP; 20 Aug 2010 00:32:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 275216.21586.bm@omp201.mail.re3.yahoo.com Received: (qmail 76659 invoked by uid 60001); 20 Aug 2010 00:32:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1282264363; bh=dqoW87Xw4jC1hhkOOVTLbKintdhN+KFI2fVXJP/AN6Y=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=X0icvtbnIKt52VIElKKtTT6nlBC2COFwQY/8ALi1Dv9r+XXzEHz+gUB8L4zmBvsEPS5upHky04tq0Rm+JS46yFZyB6WREP9zjPU7XUfUWSWihKzfFq4Qb1uWMASlGWgTexzOESeE1hJGdYOkxjJNKruD+db+aRnqqiyfBn1VVQk= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=u9fE6g4nIG0E7pZnX7shS3pmvsQC8ArM+MjbN+shdCt+p7AFPshbknQuMgpEDyXrmIeYAm9uiPIUSH5AGcuhQsBze6bHl5zc6G0B2U0CKucUH8vK0QAXLxwJLtNM/P17D0dEs7TwSPeZe1G85zpyL561D+gMle/mo7dPQPZv/Ug=; Message-ID: <161741.73319.qm@web56203.mail.re3.yahoo.com> X-YMail-OSG: .p5wuDUVM1k3l0AMzUFUqPzUvogqUnv7aoQnEQQEyKXRikE mYf.moAWF9TVphdmqpW3cP0BgRDVhOv2GDpxQtbb51s0uLDOJk2RimDoSjgX 3YXRgyzViL9cUWa1HX9brTtzJ1oGmgu84EJh2Vi3bVCj8Ir1f7dloFUN1nP4 2LoXiH6ix23491aDdcHsrlvo8F_KjrPEOFU0Zp8xqXhTWfBVAa6Zge_ArZKd AnF99eA065BX24JgDinTpmuEFsRZTmBl4lIPXmWthllzTVNyAJvHDdq4JOr2 VfT5QDnqC4DHg1fDExioeCSuGykgnxHFxoEXR9IaOggfYkAStvy28okTZg4a u63FXmGrX2rRgig7HkFThYVBLOiAFrdAz0ETwxPRryQRQpK_Z Received: from [209.131.62.113] by web56203.mail.re3.yahoo.com via HTTP; Thu, 19 Aug 2010 17:32:42 PDT X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950 References: Date: Thu, 19 Aug 2010 17:32:42 -0700 (PDT) From: "Tsz Wo \(Nicholas\), Sze" Subject: Re: [VOTE] New branch for HDFS-1052 development To: hdfs-dev@hadoop.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Do we need a vote for creating a development branch? It seems to me that we do not have such votes before. The committer just go ahead creating a branch. Nicholas ----- Original Message ---- > From: Suresh Srinivas > To: "hdfs-dev@hadoop.apache.org" > Sent: Thu, August 19, 2010 5:07:14 PM > Subject: [VOTE] New branch for HDFS-1052 development > > I am planning to create a new branch from the trunk for the work related to >HDFS-1052 - HDFS scalability using multiple namenodes/namespaces. Please see the >jira for more details. Doing the development in a separate branch will reduce >the churn on the trunk. The development will be done incrementally in the new >branch using multiple sub jiras. When the development and testing is complete, >the changes from this branch will be promoted back to trunk. > Regards, Suresh >