Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <4ABD38E3.8050706@apache.org>
Date: Fri, 25 Sep 2009 14:40:51 -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: <C6E27C4A.86E%awittenauer@linkedin.com>
In-Reply-To: <C6E27C4A.86E%awittenauer@linkedin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Allen Wittenauer wrote:
> Oh, I completely understand.  I'm just throwing in a non-developer's
> opinion... because I'm sure I'm not the only one expecting/assuming that 1.0
> == completely stable.  

If we have to live up to that expectation then we might never release 
1.0!  Frankly, I fear the longer we delay a 1.0 release the more we 
raise expectations that it will be all things.  Rather, I'd like to have 
1.0 to mean just one thing: back-compatible APIs until 2.0, with the 
expectation that there will be several 1.x releases between.  We can add 
other things to 1.0, which might push it out further, but I don't see 
how that helps things much.

Would it be materially better for you if we waited longer before calling 
a release 1.0, assuming that the same features are released in the same 
order and on the same schedule regardless of the release name?

Doug