Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Message-ID: <4F67AB88.1060001@apache.org>
Date: Mon, 19 Mar 2012 14:56:24 -0700
From: Doug Cutting <cutting@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: general@hadoop.apache.org
Subject: Re: Naming of Hadoop releases
References: <CB8CD802.2D12E%Milind.Bhandarkar@emc.com>
 <F0644DC2-2F79-437E-9086-FEF9C2B48D4C@hortonworks.com>
In-Reply-To: <F0644DC2-2F79-437E-9086-FEF9C2B48D4C@hortonworks.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 03/19/2012 02:47 PM, Arun C Murthy wrote:
> This is against the Apache Hadoop release policy on major releases i.e. only features deprecated for at least one release can be removed.

In many case the reason this happened was that features were backported
from trunk to 0.20 but not to 0.22.  In other words, its no fault of the
folks who were working on branch 0.22.  So a related policy we might add
to prevent such situations in the future might be that if you backport
something from branch n to n-2 then you ought to also be required to
backport it to branch n-1 and in general to all intervening branches.
Does that seem sensible?

Doug