Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=mime-version:content-transfer-encoding:message-id:
	content-type:to:from:subject:date:x-mailer;
	b=Dmi+xzYjNCjkS+RhBM64S3K3TSskoJBeG9UROOmWxxev/YGtB3Ds8iLluLh9Q8vA
Mime-Version: 1.0 (Apple Message framework v753)
Content-Transfer-Encoding: 7bit
Message-Id: <08438743-8BB1-434C-8772-D63DC8D8A924@yahoo-inc.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: hadoop-dev@lucene.apache.org
From: Nigel Daley <ndaley@yahoo-inc.com>
Subject: 0.16 schedule and follow-on bug fix releases
Date: Thu, 17 Jan 2008 09:07:17 -0800

To date (or at least in the past 1.5 years I've been working on  
Hadoop), our shortest timeline from feature freeze to a release vote  
has been around 4 weeks.  This time is typically spent fixing blockers.

I'd like to propose that we tighten up on what a blocker is, get the  
release out sooner, and then plan to do follow-on bug fix releases on  
a regular interval.  As your release manager, I'll sign up to  
consider a bug fix release every 2 weeks if there is a critical  
enough bug or a critical mass of bugs.  Roughly every 2 weeks, then,  
would be a window to consider a bug fix release.

For 0.16.0, can we set a goal of having all blocker committed and  
calling a vote next Thursday, Jan 24, with a blocker defined as
a) a bad regression
b) an unintended incompatibility
c) bad bugs in an important new feature

Thoughts?

Nige

PS As a reminder, 0.17.0 is scheduled for the first Friday in April  
(3 months).

PPS Monday, Jan 21 is a holiday in the US for many companies