Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of owen.omalley@gmail.com
 designates 209.85.217.215 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=xFVOSTJCkUbPvP1ZOU7k4MGKXa+IZGy7c+PY1l6j+JukcQPRzp0qMPqbBlZca9kQCW
         7NLqDipzbzTgjCb83wKBgoQ/zlqHGNymXeyugGmx7L3F1HMnn4fask5SzfLOKUO1aQkL
         u8wgJIoYUEXuNsG6ZKgVKAPrw/CnMsEGFWRYY=
MIME-Version: 1.0
In-Reply-To: <4aa34eb70907071339w7095b67fu4c65843a152b520a@mail.gmail.com>
References: <BF94FA23-1853-4832-A3ED-5A8B4B4EE5D3@yahoo-inc.com>
	 <239E9EA6-30BD-46C5-947C-61A4F2D2F6C8@yahoo-inc.com>
	 <5B8D5362-153A-4BF1-83AD-64C6D8413AD9@yahoo-inc.com>
	 <CD2E0A273BDAAD409C70BB3F48EE6A126CB41FAB80@SC-MBXC1.TheFacebook.com>
	 <4aa34eb70907071339w7095b67fu4c65843a152b520a@mail.gmail.com>
Date: Tue, 7 Jul 2009 13:49:17 -0700
Message-ID: <5f7f740b0907071349k3d381b2fi60a4baed01e15424@mail.gmail.com>
Subject: Re: [VOTE] Back-port TFile to Hadoop 0.20
From: "Owen O'Malley" <owen.omalley@gmail.com>
To: common-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=000e0cd4d8e68f7640046e23c1eb

--000e0cd4d8e68f7640046e23c1eb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On Tue, Jul 7, 2009 at 1:39 PM, Dhruba Borthakur <dhruba@gmail.com> wrote:

> I think we are trying to change an existing Apache-Hadoop process. The
> current process specifically says that a released branch cannot have new
> features checked into it.
>
> This vote seems to be proposing that "If a new feature does not change any
> existing code (other than build.xml), then it is ok to check in that
> feature
> to an existing release branch".
>
> If my understanding is right, then +1 on the above proposal.


 No, this is not changing the process.

It has always been ok to call a vote whether a new feature can be backported
on to a stable branch. The community should weigh the value of the
contribution relative to the risk of induced instability. The goal of the
prohibition against back porting features is to ensure that the stable
versions stay stable.

-- Owen

--000e0cd4d8e68f7640046e23c1eb--