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 acm@hortonworks.com designates
 209.85.212.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5D2b3ybtYy_E6kGf=_awbuMYnKSX6VPAgSkwp3DUUFeyqDQ@mail.gmail.com>
References: 
 <CAGB5D2YdXR8YgGBczjo=QmDJxwGp5dhBSGhq8uFOeAbJ4ST4Lw@mail.gmail.com>
	<7B9C5173-3793-4621-856F-66A224657434@hortonworks.com>
	<CADdVdVFrNr4MRgCQF6p=S7MeGcjYemmy7BO9xZtsCWNhQGSDgA@mail.gmail.com>
	<CAGB5D2aRxg1rQAh0cssRjMFAATghcCEwgtdnTwcv57347yjCww@mail.gmail.com>
	<CEFDBE6B-3559-418D-BC2D-F65EC80F01F7@hortonworks.com>
	<CADcMMgGumncG8ov8=wm-95=dcZ=2iiGp3CCgjdT6cUzXshR4Gg@mail.gmail.com>
	<CAGB5D2YDd0u3Ktj2FwcW1X+bWTJ5S=UURa1PL5LE95xqvuEfKQ@mail.gmail.com>
	<D88667FE-1BA1-44BE-AE66-E55D3D0CA5B8@apache.org>
	<CAGB5D2aZtWwmoDjEzdn9TZ_uvQEfMWZf5KL3GcL4wx31wkuhfw@mail.gmail.com>
	<FA27F268-9AD2-4C96-9669-FAEBD26857F5@hortonworks.com>
	<CAGB5D2b3ybtYy_E6kGf=_awbuMYnKSX6VPAgSkwp3DUUFeyqDQ@mail.gmail.com>
Date: Wed, 22 Jan 2014 18:09:40 -0800
Message-ID: 
 <CAK1ayvtUqvVaTqNBn_wykkk=QNN2TSGOceEYXFWrysd+WpuLJA@mail.gmail.com>
Subject: Re: Logistics for releasing 2.4
From: Arun Murthy <acm@hortonworks.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=047d7b3a956cf7cd7e04f099bb9f

--047d7b3a956cf7cd7e04f099bb9f
Content-Type: text/plain; charset=US-ASCII

Sounds good, thanks. I'll ping you off-thread.

Arun


On Wed, Jan 22, 2014 at 6:01 PM, Andrew Wang <andrew.wang@cloudera.com>wrote:

> Hi Arun, thanks for the reply. I hope that I've come across as an earnest
> and motivated contributor who wants to help make high-quality releases.
> Volunteering myself as RM and pushing for a 2.4 was not a reflection on
> your stewardship of 2.x so far. I know it's a lot of work.
>
> I didn't mean to suggest 12 releases per year. I was trying to couch my
> terminology with "monthly-ish" and "regular cadence". I must have missed
> the email thread where we decided on this, but 6-8 weeks per cycle is 100%
> fine with me. I obviously don't want meaningless releases just for the sake
> of releases, but I think HDFS-2832, HDFS-4949, and all the other
> improvements in branch-2 add enough value that cutting something is not
> meaningless.
>
> My impression of the two YARN JIRAs is that they're still roughly a month
> from being prod-ready, which is why I figured they could wait 6 weeks for
> the next 2.x. That was also not a slight on the YARN developers, it's that
> I think we should follow through if we're serious about a regular release
> cadence. As you allude to, we need to get used to slipping features to the
> next release. Symlinks one such example that I've personally been involved
> with, so I do understand.
>
> As an aside, I think this means that we should be more judicious about
> branch-2 merges in the future, since a regular cadence means branch-2
> should stay in a releasable state. I hope we can avoid burdonsome code
> divergence through "hard-disable" patches (e.g. symlinks) or pushing down
> just refactors (sort of like HDFS-2832), but that remains to be seen.
>
> I can abandon the 2.3rc, and then release current branch-2 as 2.3. Would
> > that be better?
> >
>
> That'd be great. All I'm after here is a regular release cadence with good
> integration testing, so if you're willing to RM it, awesome. As I stated
> way back in the thread, feel free to email me if you think I can help with
> the release process.
>
> Thanks,
> Andrew
>


-- 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

--047d7b3a956cf7cd7e04f099bb9f--