Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <4A981563.8000508@apache.org>
Date: Fri, 28 Aug 2009 10:35:31 -0700
From: Doug Cutting <cutting@apache.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: common-dev@hadoop.apache.org
Subject: Re: Towards Hadoop 1.0:  Stronger API Compatibility from 0.21 onwards
References: <0E8A0D2C-C5B9-4E11-87D6-44AA5DE5BE2A@gmail.com>
In-Reply-To: <0E8A0D2C-C5B9-4E11-87D6-44AA5DE5BE2A@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sanjay Radia wrote:
> I propose that we honor the compatibility of stable interfaces  from 
> release 0.21 onwards;
> i.e. apply the same post 1.0 rules to pre-1.0 releases.

I think that makes 0.21 effectively 1.0.  The hallmark of 1.0 will be 
our promise not to change APIs incompatibly until 2.0.  If we make that 
promise sooner, then we're just accelerating 1.0.

I understood that the plan was to add inter-release wire compatibility 
after 1.0, somewhere in the 1.x series of releases.  So, e.g., if we add 
it in 1.1, then a 1.1 and 1.2 cluster would be able to make RPCs to one 
another, but 1.0 would not be able to make RPCs to these releases or 
vice versa.

Doug