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 3D24F119C3 for ; Fri, 10 May 2013 02:40:58 +0000 (UTC) Received: (qmail 30168 invoked by uid 500); 10 May 2013 02:40:56 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 30063 invoked by uid 500); 10 May 2013 02:40:56 -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 30054 invoked by uid 99); 10 May 2013 02:40:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 02:40:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jrottinghuis@gmail.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 02:40:49 +0000 Received: by mail-pa0-f44.google.com with SMTP id jh10so2582254pab.3 for ; Thu, 09 May 2013 19:40:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=kP2RItpDcR0gSAAB/aQ7lslTRMA2i9yxcGO1uBhJj6g=; b=UMQe29hyZsR4Dl04zaXCZBK8+bwdbQTWrrbfzTOOc73ehed6BNAmA7LGA1ZFHnZv/C bvdWo86FOvVihB/Y5w/K9zrLFiI5V8deGlt+4MTyza59XVYOH2v494G29kWNj40De7J2 svVPEL6rVdlH/tTe/BUm5KZkvhkNlXKn4vXoMl0IXy7ddyo+scBLVap4tOEOkcQNhCrV UTXSmQwuMiz5j0cV8bbxAN99mkN7dIzaWTU/vwB+cc+tMa7qqu7DcAiS9mnuSS1wwXEA iGPwTJzpFp8XY83JI75Hbl4tleADH2FvFJiz68agaUCmRLXkS1lZ5lvGcvpeP1a0eeL/ v1EA== MIME-Version: 1.0 X-Received: by 10.68.12.37 with SMTP id v5mr1106870pbb.30.1368153628026; Thu, 09 May 2013 19:40:28 -0700 (PDT) Received: by 10.68.51.170 with HTTP; Thu, 9 May 2013 19:40:27 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 May 2013 19:40:27 -0700 Message-ID: Subject: Re: [VOTE] Release plan for Hadoop 2.0.5 From: "J. Rottinghuis" To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=bcaec51f90c9ff2d2d04dc541622 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51f90c9ff2d2d04dc541622 Content-Type: text/plain; charset=ISO-8859-1 +1 (non-binding) to stabilize 2.0, and add new features only after a stable release. I understand that what constitutes as "new feature" versus "stabilizing" is subjective. Thanks, Joep On May 1, 2013, at 12:53 PM, Konstantin Shvachko wrote: > > > Please vote on the following plan for Hadoop release 2.0.5 > > - bug fixes encountered in current release 2.0.4-alpha > > - make all API changes to allow freezing them post 2.0.5 > > - no new features > > > > As discussed on @dev thread > > http://s.apache.org/fs > > this will allow to stabilize 2.0 branch in a short and predictable period > > of time. > > This enables a powerful option to have the release tested at Yahoo scale. > > The plan is to follow up with 2.1.0 - the stable release. > > New features can and should be added on top of the stable release once it > > is out. > > > > Hadoop by-laws: > > http://hadoop.apache.org/bylaws.html > > > > "Release Plan > > Defines the timetable and actions for a release. The plan also nominates > a > > Release Manager. > > Lazy majority of active committers" > > > > assume nomination of a Release Manager with the plan. > > It would be really good if Arun continues if this plan is adopted. > > We can return to the RM topic if not. > > > > The vote will run for 7 days until next Wed, May 8th. > > > > Thanks, > > --Konstantin > > --bcaec51f90c9ff2d2d04dc541622--