Re: continuing releases on Apache Hadoop 2.6.x

[Junping Du]

Thanks Vinod!

I went through all 31 fixes (Common: 8, HDFS: 6, MAPREDUCE: 8, YARN: 9) landed 
on branch-2.6? now, and all outstanding patches (>=5KB) are listed below and 
they are all bug fix.

Haven't found any high risky patches so far but I noticed we have 3 significant 
fixes (MAPREDUCE-5948, MAPREDUCE-6481 and MAPREDUCE-6549) for LineRecordReader. 
 Among them, MAPREDUCE-5948 and MAPREDUCE-6481 are completed fixes and we will 
ship them in 2.7.2, so I think there is no risk with them. MAPREDUCE-6549, 
together with an open JIRA: MAPREDUCE-6558, sounds like fix the same issue for 
uncompressed/compressed input file. I already ping the JIRA owners to get 
suggestions on if we could release MAPREDUCE-6549 independently or together 
with MAPREDUCE-6558 in next release.

I already pinged all owners for open JIRAs that targeted for 2.6.3 to move it 
to 2.6.4. Based on the feedback from JIRAs (and voices here too), I will create 
branch-2.6.3 in next 1 day or 2. Thanks!?


List of Outstanding Patches:


HADOOP-10134 [JDK8] Fix Javadoc errors caused by incorrect or illegal tags 
in doc comments. (apurtell via stevel) 38K

HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in 
commitBlock. (Chang Li via zhz) 12K
HDFS-9470. Encryption zone on root not loaded from fsimage after NN 
restart. (Xiao Chen via wang) 5K

MAPREDUCE-6273. HistoryFileManager should check whether summaryFile exists 
to avoid FileNotFoundException causing HistoryFileInfo into MOVE_FAILED state. 
(zhihai xu via devaraj) 5K
MAPREDUCE-5948. org.apache.hadoop.mapred.LineRecordReader does not handle 
multibyte record delimiters well (Vinayakumar B, Rushabh Shah, and Akira 
AJISAKA via jlowe) 20K
MAPREDUCE-6481. LineRecordReader may give incomplete record and wrong 
position/key information for uncompressed input sometimes. (Zhihai Xu via 
jlowe) 19K
MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate 
records (wilfreds via rkanter) 31K

YARN-2859. ApplicationHistoryServer binds to default port 8188 in 
MiniYARNCluster.(Vinod Kumar Vavilapalli via xgong) 6K (with addendum)
YARN-4344. NMs reconnecting with changed capabilities can lead to wrong 
cluster resource calculations (Varun Vasudev via jlowe) 12K
YARN-3925. ContainerLogsUtils#getContainerLogFile fails to read container 
log files from full disks. (zhihai xu via jlowe) 7K


Thanks,


Junping



From: Vinod Kumar Vavilapalli 
Sent: Monday, November 30, 2015 9:23 PM
To: Junping Du
Cc: Sangjin Lee; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; 
Hadoop Common; hdfs-...@hadoop.apache.org; Haohui Mai; Chris Trezzo
Subject: Re: continuing releases on Apache Hadoop 2.6.x

+1, this sounds good to me.

Thanks
+Vinod


On Nov 25, 2015, at 11:44 AM, Junping Du 
mailto:j...@hortonworks.com>> wrote:

May be we should quickly go through landed patches in 2.6.3 list and postpone 
any risky patches to 2.6.4?

Re: continuing releases on Apache Hadoop 2.6.x

[Vinod Kumar Vavilapalli]

+1, this sounds good to me.

Thanks
+Vinod


> On Nov 25, 2015, at 11:44 AM, Junping Du  wrote:
> 
> May be we should quickly go through landed patches in 2.6.3 list and postpone 
> any risky patches to 2.6.4?
> 

Re: continuing releases on Apache Hadoop 2.6.x

[Junping Du]

Thanks Sangjin for comments. This is also an option that I thought before. 
However, a single-fix release sounds a little overkill, especially after 
looking at the release scope of Apache commons-collections 3.3.2 
(https://commons.apache.org/proper/commons-collections/release_3_2_2.html) 
which actually get affected more directly.

May be we should quickly go through landed patches in 2.6.3 list and postpone 
any risky patches to 2.6.4?


Thanks,


Junping


From: sjl...@gmail.com  on behalf of Sangjin Lee 

Sent: Wednesday, November 25, 2015 6:55 PM
To: Junping Du
Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Hadoop Common; 
hdfs-...@hadoop.apache.org; Vinod Vavilapalli; Haohui Mai; Chris Trezzo
Subject: Re: continuing releases on Apache Hadoop 2.6.x

If the speed and clarity are important for the security release, then I would 
argue for a single-fix release (2.6.2 + HADOOP-12577 only). The verification of 
the RC and the associated release process would be so much faster.

We would need to do a little bit of special branch creation etc., but it would 
still be very straightforward. My 2 cents.

Sangjin

On Wed, Nov 25, 2015 at 10:23 AM, Junping Du 
mailto:j...@hortonworks.com>> wrote:
Given there is a critical security fix (HADOOP-12577) coming, I think we should 
move faster on releasing 2.6.3.
I would propose to freeze nominating new fixes to 2.6.3 unless they are 
critical enough as blocker. We can nominate more fixes later in 2.6.4. Thoughts?

Thanks,

Junping

From: sjl...@gmail.com<mailto:sjl...@gmail.com> 
mailto:sjl...@gmail.com>> on behalf of Sangjin Lee 
mailto:sj...@apache.org>>
Sent: Friday, November 20, 2015 7:07 PM
To: mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>
Cc: Hadoop Common; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; 
hdfs-...@hadoop.apache.org<mailto:hdfs-...@hadoop.apache.org>
Subject: Re: continuing releases on Apache Hadoop 2.6.x

It would be great if we can get enough number of fixes by early December.
18 seems bit on the low side, but if we lose this window it won't be until
next year.

As for the release management, thanks Chris, Junping, and Haohui for
volunteering! I'll reach out to you to discuss what we do with 2.6.3. I
assume we will have more maintenance releases in the 2.6.x line, so there
will be more opportunities. We do need one person with PMC privileges to be
able to go through all the release management steps without assistance,
which I learned last time.

Regards,
Sangjin

On Fri, Nov 20, 2015 at 10:03 AM, Sean Busbey 
mailto:bus...@cloudera.com>> wrote:

> Early december would be great, presuming the RC process doesn't take too
> long. By then it'll already have over a month since the 2.6.2 release and
> I'm sure the folks contributing the 18 patches we already have in would
> like to see their work out there.
>
> On Fri, Nov 20, 2015 at 7:51 AM, Junping Du 
> mailto:j...@hortonworks.com>> wrote:
>
> > +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> > patches since recently release 2.6.2.
> > We should nominate more fixes and wait a while for the feedback on 2.6.2.
> >
> > Thanks,
> >
> > Junping
> > 
> > From: Vinod Vavilapalli 
> > mailto:vino...@hortonworks.com>>
> > Sent: Thursday, November 19, 2015 11:34 PM
> > To: yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
> > Cc: common-dev@hadoop.apache.org<mailto:common-dev@hadoop.apache.org>; 
> > hdfs-...@hadoop.apache.org<mailto:hdfs-...@hadoop.apache.org>;
> > mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>
> > Subject: Re: continuing releases on Apache Hadoop 2.6.x
> >
> > I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> > will have a reasonable number of fixes if we start an RC early december.
> >
> > In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> > critical list and see if it makes sense to backport any of those into
> 2.6.3.
> >
> > +Vinod
> >
> >
> > On Nov 17, 2015, at 5:10 PM, Sangjin Lee 
> > mailto:sj...@apache.org> > sj...@apache.org<mailto:sj...@apache.org>>> wrote:
> >
> > I'd like to pick up this email discussion again. It is time that we
> started
> > thinking about the next release in the 2.6.x line. IMO we want to walk
> the
> > balance between maintaining a reasonable release cadence and getting a
> good
> > amount of high-quality fixes. The timeframe is a little tricky as the
> > holidays are approaching. If we have enough fixes accumulated in
> > branch-2.6, some time early December might be a good target for cutting
> the
> > first release candidate. Once we miss that window, I think we are looking
> > at next January. I'd like to hear your thoughts on this.
> >
> >
>
>
> --
> Sean
>

Re: continuing releases on Apache Hadoop 2.6.x

[Sangjin Lee]

If the speed and clarity are important for the security release, then I
would argue for a single-fix release (2.6.2 + HADOOP-12577 only). The
verification of the RC and the associated release process would be so much
faster.

We would need to do a little bit of special branch creation etc., but it
would still be very straightforward. My 2 cents.

Sangjin

On Wed, Nov 25, 2015 at 10:23 AM, Junping Du  wrote:

> Given there is a critical security fix (HADOOP-12577) coming, I think we
> should move faster on releasing 2.6.3.
> I would propose to freeze nominating new fixes to 2.6.3 unless they are
> critical enough as blocker. We can nominate more fixes later in 2.6.4.
> Thoughts?
>
> Thanks,
>
> Junping
> 
> From: sjl...@gmail.com  on behalf of Sangjin Lee <
> sj...@apache.org>
> Sent: Friday, November 20, 2015 7:07 PM
> To: mapreduce-...@hadoop.apache.org
> Cc: Hadoop Common; yarn-...@hadoop.apache.org; hdfs-...@hadoop.apache.org
> Subject: Re: continuing releases on Apache Hadoop 2.6.x
>
> It would be great if we can get enough number of fixes by early December.
> 18 seems bit on the low side, but if we lose this window it won't be until
> next year.
>
> As for the release management, thanks Chris, Junping, and Haohui for
> volunteering! I'll reach out to you to discuss what we do with 2.6.3. I
> assume we will have more maintenance releases in the 2.6.x line, so there
> will be more opportunities. We do need one person with PMC privileges to be
> able to go through all the release management steps without assistance,
> which I learned last time.
>
> Regards,
> Sangjin
>
> On Fri, Nov 20, 2015 at 10:03 AM, Sean Busbey  wrote:
>
> > Early december would be great, presuming the RC process doesn't take too
> > long. By then it'll already have over a month since the 2.6.2 release and
> > I'm sure the folks contributing the 18 patches we already have in would
> > like to see their work out there.
> >
> > On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:
> >
> > > +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> > > patches since recently release 2.6.2.
> > > We should nominate more fixes and wait a while for the feedback on
> 2.6.2.
> > >
> > > Thanks,
> > >
> > > Junping
> > > 
> > > From: Vinod Vavilapalli 
> > > Sent: Thursday, November 19, 2015 11:34 PM
> > > To: yarn-...@hadoop.apache.org
> > > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > > mapreduce-...@hadoop.apache.org
> > > Subject: Re: continuing releases on Apache Hadoop 2.6.x
> > >
> > > I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like
> we
> > > will have a reasonable number of fixes if we start an RC early
> december.
> > >
> > > In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> > > critical list and see if it makes sense to backport any of those into
> > 2.6.3.
> > >
> > > +Vinod
> > >
> > >
> > > On Nov 17, 2015, at 5:10 PM, Sangjin Lee  > > sj...@apache.org>> wrote:
> > >
> > > I'd like to pick up this email discussion again. It is time that we
> > started
> > > thinking about the next release in the 2.6.x line. IMO we want to walk
> > the
> > > balance between maintaining a reasonable release cadence and getting a
> > good
> > > amount of high-quality fixes. The timeframe is a little tricky as the
> > > holidays are approaching. If we have enough fixes accumulated in
> > > branch-2.6, some time early December might be a good target for cutting
> > the
> > > first release candidate. Once we miss that window, I think we are
> looking
> > > at next January. I'd like to hear your thoughts on this.
> > >
> > >
> >
> >
> > --
> > Sean
> >
>

Re: continuing releases on Apache Hadoop 2.6.x

[Junping Du]

Given there is a critical security fix (HADOOP-12577) coming, I think we should 
move faster on releasing 2.6.3. 
I would propose to freeze nominating new fixes to 2.6.3 unless they are 
critical enough as blocker. We can nominate more fixes later in 2.6.4. Thoughts?

Thanks,

Junping

From: sjl...@gmail.com  on behalf of Sangjin Lee 

Sent: Friday, November 20, 2015 7:07 PM
To: mapreduce-...@hadoop.apache.org
Cc: Hadoop Common; yarn-...@hadoop.apache.org; hdfs-...@hadoop.apache.org
Subject: Re: continuing releases on Apache Hadoop 2.6.x

It would be great if we can get enough number of fixes by early December.
18 seems bit on the low side, but if we lose this window it won't be until
next year.

As for the release management, thanks Chris, Junping, and Haohui for
volunteering! I'll reach out to you to discuss what we do with 2.6.3. I
assume we will have more maintenance releases in the 2.6.x line, so there
will be more opportunities. We do need one person with PMC privileges to be
able to go through all the release management steps without assistance,
which I learned last time.

Regards,
Sangjin

On Fri, Nov 20, 2015 at 10:03 AM, Sean Busbey  wrote:

> Early december would be great, presuming the RC process doesn't take too
> long. By then it'll already have over a month since the 2.6.2 release and
> I'm sure the folks contributing the 18 patches we already have in would
> like to see their work out there.
>
> On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:
>
> > +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> > patches since recently release 2.6.2.
> > We should nominate more fixes and wait a while for the feedback on 2.6.2.
> >
> > Thanks,
> >
> > Junping
> > 
> > From: Vinod Vavilapalli 
> > Sent: Thursday, November 19, 2015 11:34 PM
> > To: yarn-...@hadoop.apache.org
> > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > mapreduce-...@hadoop.apache.org
> > Subject: Re: continuing releases on Apache Hadoop 2.6.x
> >
> > I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> > will have a reasonable number of fixes if we start an RC early december.
> >
> > In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> > critical list and see if it makes sense to backport any of those into
> 2.6.3.
> >
> > +Vinod
> >
> >
> > On Nov 17, 2015, at 5:10 PM, Sangjin Lee  > sj...@apache.org>> wrote:
> >
> > I'd like to pick up this email discussion again. It is time that we
> started
> > thinking about the next release in the 2.6.x line. IMO we want to walk
> the
> > balance between maintaining a reasonable release cadence and getting a
> good
> > amount of high-quality fixes. The timeframe is a little tricky as the
> > holidays are approaching. If we have enough fixes accumulated in
> > branch-2.6, some time early December might be a good target for cutting
> the
> > first release candidate. Once we miss that window, I think we are looking
> > at next January. I'd like to hear your thoughts on this.
> >
> >
>
>
> --
> Sean
>

Re: continuing releases on Apache Hadoop 2.6.x

[Sangjin Lee]

It would be great if we can get enough number of fixes by early December.
18 seems bit on the low side, but if we lose this window it won't be until
next year.

As for the release management, thanks Chris, Junping, and Haohui for
volunteering! I'll reach out to you to discuss what we do with 2.6.3. I
assume we will have more maintenance releases in the 2.6.x line, so there
will be more opportunities. We do need one person with PMC privileges to be
able to go through all the release management steps without assistance,
which I learned last time.

Regards,
Sangjin

On Fri, Nov 20, 2015 at 10:03 AM, Sean Busbey  wrote:

> Early december would be great, presuming the RC process doesn't take too
> long. By then it'll already have over a month since the 2.6.2 release and
> I'm sure the folks contributing the 18 patches we already have in would
> like to see their work out there.
>
> On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:
>
> > +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> > patches since recently release 2.6.2.
> > We should nominate more fixes and wait a while for the feedback on 2.6.2.
> >
> > Thanks,
> >
> > Junping
> > 
> > From: Vinod Vavilapalli 
> > Sent: Thursday, November 19, 2015 11:34 PM
> > To: yarn-...@hadoop.apache.org
> > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > mapreduce-...@hadoop.apache.org
> > Subject: Re: continuing releases on Apache Hadoop 2.6.x
> >
> > I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> > will have a reasonable number of fixes if we start an RC early december.
> >
> > In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> > critical list and see if it makes sense to backport any of those into
> 2.6.3.
> >
> > +Vinod
> >
> >
> > On Nov 17, 2015, at 5:10 PM, Sangjin Lee  > sj...@apache.org>> wrote:
> >
> > I'd like to pick up this email discussion again. It is time that we
> started
> > thinking about the next release in the 2.6.x line. IMO we want to walk
> the
> > balance between maintaining a reasonable release cadence and getting a
> good
> > amount of high-quality fixes. The timeframe is a little tricky as the
> > holidays are approaching. If we have enough fixes accumulated in
> > branch-2.6, some time early December might be a good target for cutting
> the
> > first release candidate. Once we miss that window, I think we are looking
> > at next January. I'd like to hear your thoughts on this.
> >
> >
>
>
> --
> Sean
>

Re: continuing releases on Apache Hadoop 2.6.x

[Sean Busbey]

Early december would be great, presuming the RC process doesn't take too
long. By then it'll already have over a month since the 2.6.2 release and
I'm sure the folks contributing the 18 patches we already have in would
like to see their work out there.

On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:

> +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> patches since recently release 2.6.2.
> We should nominate more fixes and wait a while for the feedback on 2.6.2.
>
> Thanks,
>
> Junping
> 
> From: Vinod Vavilapalli 
> Sent: Thursday, November 19, 2015 11:34 PM
> To: yarn-...@hadoop.apache.org
> Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org
> Subject: Re: continuing releases on Apache Hadoop 2.6.x
>
> I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> will have a reasonable number of fixes if we start an RC early december.
>
> In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> critical list and see if it makes sense to backport any of those into 2.6.3.
>
> +Vinod
>
>
> On Nov 17, 2015, at 5:10 PM, Sangjin Lee  sj...@apache.org>> wrote:
>
> I'd like to pick up this email discussion again. It is time that we started
> thinking about the next release in the 2.6.x line. IMO we want to walk the
> balance between maintaining a reasonable release cadence and getting a good
> amount of high-quality fixes. The timeframe is a little tricky as the
> holidays are approaching. If we have enough fixes accumulated in
> branch-2.6, some time early December might be a good target for cutting the
> first release candidate. Once we miss that window, I think we are looking
> at next January. I'd like to hear your thoughts on this.
>
>


-- 
Sean

Re: continuing releases on Apache Hadoop 2.6.x

[Junping Du]

+1. Early Dec sounds too early for 2.6.3 release given we only have 18 patches 
since recently release 2.6.2.
We should nominate more fixes and wait a while for the feedback on 2.6.2.

Thanks,

Junping

From: Vinod Vavilapalli 
Sent: Thursday, November 19, 2015 11:34 PM
To: yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: continuing releases on Apache Hadoop 2.6.x

I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we will 
have a reasonable number of fixes if we start an RC early december.

In the mean while, we should also review 2.7.3 and 2.8.0 blocker / critical 
list and see if it makes sense to backport any of those into 2.6.3.

+Vinod


On Nov 17, 2015, at 5:10 PM, Sangjin Lee 
mailto:sj...@apache.org>> wrote:

I'd like to pick up this email discussion again. It is time that we started
thinking about the next release in the 2.6.x line. IMO we want to walk the
balance between maintaining a reasonable release cadence and getting a good
amount of high-quality fixes. The timeframe is a little tricky as the
holidays are approaching. If we have enough fixes accumulated in
branch-2.6, some time early December might be a good target for cutting the
first release candidate. Once we miss that window, I think we are looking
at next January. I'd like to hear your thoughts on this.

Re: continuing releases on Apache Hadoop 2.6.x

[Vinod Vavilapalli]

I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we will 
have a reasonable number of fixes if we start an RC early december.

In the mean while, we should also review 2.7.3 and 2.8.0 blocker / critical 
list and see if it makes sense to backport any of those into 2.6.3.

+Vinod


On Nov 17, 2015, at 5:10 PM, Sangjin Lee 
mailto:sj...@apache.org>> wrote:

I'd like to pick up this email discussion again. It is time that we started
thinking about the next release in the 2.6.x line. IMO we want to walk the
balance between maintaining a reasonable release cadence and getting a good
amount of high-quality fixes. The timeframe is a little tricky as the
holidays are approaching. If we have enough fixes accumulated in
branch-2.6, some time early December might be a good target for cutting the
first release candidate. Once we miss that window, I think we are looking
at next January. I'd like to hear your thoughts on this.

Re: continuing releases on Apache Hadoop 2.6.x

[Haohui Mai]

Hi,

I can help on releasing 2.6.3.

~Haohui


On Wed, Nov 18, 2015 at 8:20 AM, Chris Trezzo  wrote:
> Thanks Junping for the clarification! It was not my intention to violate
> the rules. I would be happy to work with you and help you manage the
> release in whatever way is most effective.
>
> Chris
>
> On Wednesday, November 18, 2015, Junping Du  wrote:
>
>> Thanks Chris Trezzo for volunteer on helping 2.6.3 release. I think
>> Sangjin was asking for a committer to serve as release manager for 2.6.3
>> according to Apache rules:
>> http://www.apache.org/dev/release-publishing.html.
>> I would like to serve as that role to work closely with you and Sangjin on
>> 2.6.3 release if no objects from others.
>>
>> Thanks,
>>
>> Junping
>> 
>> From: Chris Trezzo >
>> Sent: Wednesday, November 18, 2015 1:13 AM
>> To: yarn-...@hadoop.apache.org 
>> Cc: common-dev@hadoop.apache.org ;
>> hdfs-...@hadoop.apache.org ; mapreduce-...@hadoop.apache.org
>> 
>> Subject: Re: continuing releases on Apache Hadoop 2.6.x
>>
>> Hi Sangjin,
>>
>> I would be happy to volunteer to work with you as a release manager for
>> 2.6.3. Shooting for a time in early December seems reasonable to me. I also
>> agree that if we miss that window, January would be the next best option.
>>
>> Thanks,
>> Chris
>>
>> On Tue, Nov 17, 2015 at 5:10 PM, Sangjin Lee > > wrote:
>>
>> > I'd like to pick up this email discussion again. It is time that we
>> started
>> > thinking about the next release in the 2.6.x line. IMO we want to walk
>> the
>> > balance between maintaining a reasonable release cadence and getting a
>> good
>> > amount of high-quality fixes. The timeframe is a little tricky as the
>> > holidays are approaching. If we have enough fixes accumulated in
>> > branch-2.6, some time early December might be a good target for cutting
>> the
>> > first release candidate. Once we miss that window, I think we are looking
>> > at next January. I'd like to hear your thoughts on this.
>> >
>> > It'd be good if someone can volunteer for the release manager for 2.6.3.
>> > I'd be happy to help out in any way I can. Thanks!
>> >
>> > Regards,
>> > Sangjin
>> >
>> > On Mon, Nov 2, 2015 at 11:45 AM, Vinod Vavilapalli <
>> > vino...@hortonworks.com >
>> > wrote:
>> >
>> > > Just to stress on the following, it is very important that any critical
>> > > bug-fixes that we push into 2.8.0 or even trunk, we should consider
>> them
>> > > for 2.6.3 and 2.7.3 if it makes sense. This is the only way we can
>> avoid
>> > > extremely long release cycles like that of 2.6.1.
>> > >
>> > > Also, to clarify a little, use Target-version if you want a discussion
>> of
>> > > the backport, but if you do end up backporting patches after that, you
>> > > should set the fix-version to be 2.6.1.
>> > >
>> > > Thanks
>> > > +Vinod
>> > >
>> > >
>> > > > On Nov 2, 2015, at 11:29 AM, Sangjin Lee > > wrote:
>> > > >
>> > > > As you may have seen, 2.6.2 is out
>> > > > <http://markmail.org/thread/yw53xgz6wzpqnclt>. I have also
>> retargeted
>> > > all
>> > > > open issues that were targeted for 2.6.2 to 2.6.3.
>> > > >
>> > > > Continuing the discussion in the email thread here
>> > > > <http://markmail.org/thread/ofjlzurok223bzyi>, I'd like us to
>> maintain
>> > > the
>> > > > cadence of monthly point releases in the 2.6.x line. It would be
>> great
>> > if
>> > > > we can have 2.6.3 released before the year-end holidays.
>> > > >
>> > > > If you have any bugfixes and improvements that are targeted for 2.7.x
>> > (or
>> > > > 2.8) that you think are applicable to 2.6.x, please *set the target
>> > > version
>> > > > to 2.6.3* and merge them to branch-2.6. Please use your judgment in
>> > terms
>> > > > of the applicability and quality of the changes so that we can ensure
>> > > each
>> > > > point release is consistently better quality than the previous one.
>> > > Thanks
>> > > > everyone!
>> > > >
>> > > > Regards,
>> > > > Sangjin
>> > >
>> > >
>> >
>>

Re: continuing releases on Apache Hadoop 2.6.x

[Chris Trezzo]

Thanks Junping for the clarification! It was not my intention to violate
the rules. I would be happy to work with you and help you manage the
release in whatever way is most effective.

Chris

On Wednesday, November 18, 2015, Junping Du  wrote:

> Thanks Chris Trezzo for volunteer on helping 2.6.3 release. I think
> Sangjin was asking for a committer to serve as release manager for 2.6.3
> according to Apache rules:
> http://www.apache.org/dev/release-publishing.html.
> I would like to serve as that role to work closely with you and Sangjin on
> 2.6.3 release if no objects from others.
>
> Thanks,
>
> Junping
> 
> From: Chris Trezzo >
> Sent: Wednesday, November 18, 2015 1:13 AM
> To: yarn-...@hadoop.apache.org 
> Cc: common-dev@hadoop.apache.org ;
> hdfs-...@hadoop.apache.org ; mapreduce-...@hadoop.apache.org
> 
> Subject: Re: continuing releases on Apache Hadoop 2.6.x
>
> Hi Sangjin,
>
> I would be happy to volunteer to work with you as a release manager for
> 2.6.3. Shooting for a time in early December seems reasonable to me. I also
> agree that if we miss that window, January would be the next best option.
>
> Thanks,
> Chris
>
> On Tue, Nov 17, 2015 at 5:10 PM, Sangjin Lee  > wrote:
>
> > I'd like to pick up this email discussion again. It is time that we
> started
> > thinking about the next release in the 2.6.x line. IMO we want to walk
> the
> > balance between maintaining a reasonable release cadence and getting a
> good
> > amount of high-quality fixes. The timeframe is a little tricky as the
> > holidays are approaching. If we have enough fixes accumulated in
> > branch-2.6, some time early December might be a good target for cutting
> the
> > first release candidate. Once we miss that window, I think we are looking
> > at next January. I'd like to hear your thoughts on this.
> >
> > It'd be good if someone can volunteer for the release manager for 2.6.3.
> > I'd be happy to help out in any way I can. Thanks!
> >
> > Regards,
> > Sangjin
> >
> > On Mon, Nov 2, 2015 at 11:45 AM, Vinod Vavilapalli <
> > vino...@hortonworks.com >
> > wrote:
> >
> > > Just to stress on the following, it is very important that any critical
> > > bug-fixes that we push into 2.8.0 or even trunk, we should consider
> them
> > > for 2.6.3 and 2.7.3 if it makes sense. This is the only way we can
> avoid
> > > extremely long release cycles like that of 2.6.1.
> > >
> > > Also, to clarify a little, use Target-version if you want a discussion
> of
> > > the backport, but if you do end up backporting patches after that, you
> > > should set the fix-version to be 2.6.1.
> > >
> > > Thanks
> > > +Vinod
> > >
> > >
> > > > On Nov 2, 2015, at 11:29 AM, Sangjin Lee  > wrote:
> > > >
> > > > As you may have seen, 2.6.2 is out
> > > > <http://markmail.org/thread/yw53xgz6wzpqnclt>. I have also
> retargeted
> > > all
> > > > open issues that were targeted for 2.6.2 to 2.6.3.
> > > >
> > > > Continuing the discussion in the email thread here
> > > > <http://markmail.org/thread/ofjlzurok223bzyi>, I'd like us to
> maintain
> > > the
> > > > cadence of monthly point releases in the 2.6.x line. It would be
> great
> > if
> > > > we can have 2.6.3 released before the year-end holidays.
> > > >
> > > > If you have any bugfixes and improvements that are targeted for 2.7.x
> > (or
> > > > 2.8) that you think are applicable to 2.6.x, please *set the target
> > > version
> > > > to 2.6.3* and merge them to branch-2.6. Please use your judgment in
> > terms
> > > > of the applicability and quality of the changes so that we can ensure
> > > each
> > > > point release is consistently better quality than the previous one.
> > > Thanks
> > > > everyone!
> > > >
> > > > Regards,
> > > > Sangjin
> > >
> > >
> >
>

Re: continuing releases on Apache Hadoop 2.6.x

[Junping Du]

Thanks Chris Trezzo for volunteer on helping 2.6.3 release. I think Sangjin was 
asking for a committer to serve as release manager for 2.6.3 according to 
Apache rules: http://www.apache.org/dev/release-publishing.html. 
I would like to serve as that role to work closely with you and Sangjin on 
2.6.3 release if no objects from others.

Thanks,

Junping

From: Chris Trezzo 
Sent: Wednesday, November 18, 2015 1:13 AM
To: yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: continuing releases on Apache Hadoop 2.6.x

Hi Sangjin,

I would be happy to volunteer to work with you as a release manager for
2.6.3. Shooting for a time in early December seems reasonable to me. I also
agree that if we miss that window, January would be the next best option.

Thanks,
Chris

On Tue, Nov 17, 2015 at 5:10 PM, Sangjin Lee  wrote:

> I'd like to pick up this email discussion again. It is time that we started
> thinking about the next release in the 2.6.x line. IMO we want to walk the
> balance between maintaining a reasonable release cadence and getting a good
> amount of high-quality fixes. The timeframe is a little tricky as the
> holidays are approaching. If we have enough fixes accumulated in
> branch-2.6, some time early December might be a good target for cutting the
> first release candidate. Once we miss that window, I think we are looking
> at next January. I'd like to hear your thoughts on this.
>
> It'd be good if someone can volunteer for the release manager for 2.6.3.
> I'd be happy to help out in any way I can. Thanks!
>
> Regards,
> Sangjin
>
> On Mon, Nov 2, 2015 at 11:45 AM, Vinod Vavilapalli <
> vino...@hortonworks.com>
> wrote:
>
> > Just to stress on the following, it is very important that any critical
> > bug-fixes that we push into 2.8.0 or even trunk, we should consider them
> > for 2.6.3 and 2.7.3 if it makes sense. This is the only way we can avoid
> > extremely long release cycles like that of 2.6.1.
> >
> > Also, to clarify a little, use Target-version if you want a discussion of
> > the backport, but if you do end up backporting patches after that, you
> > should set the fix-version to be 2.6.1.
> >
> > Thanks
> > +Vinod
> >
> >
> > > On Nov 2, 2015, at 11:29 AM, Sangjin Lee  wrote:
> > >
> > > As you may have seen, 2.6.2 is out
> > > <http://markmail.org/thread/yw53xgz6wzpqnclt>. I have also retargeted
> > all
> > > open issues that were targeted for 2.6.2 to 2.6.3.
> > >
> > > Continuing the discussion in the email thread here
> > > <http://markmail.org/thread/ofjlzurok223bzyi>, I'd like us to maintain
> > the
> > > cadence of monthly point releases in the 2.6.x line. It would be great
> if
> > > we can have 2.6.3 released before the year-end holidays.
> > >
> > > If you have any bugfixes and improvements that are targeted for 2.7.x
> (or
> > > 2.8) that you think are applicable to 2.6.x, please *set the target
> > version
> > > to 2.6.3* and merge them to branch-2.6. Please use your judgment in
> terms
> > > of the applicability and quality of the changes so that we can ensure
> > each
> > > point release is consistently better quality than the previous one.
> > Thanks
> > > everyone!
> > >
> > > Regards,
> > > Sangjin
> >
> >
>

Re: continuing releases on Apache Hadoop 2.6.x

[Chris Trezzo]

Hi Sangjin,

I would be happy to volunteer to work with you as a release manager for
2.6.3. Shooting for a time in early December seems reasonable to me. I also
agree that if we miss that window, January would be the next best option.

Thanks,
Chris

On Tue, Nov 17, 2015 at 5:10 PM, Sangjin Lee  wrote:

> I'd like to pick up this email discussion again. It is time that we started
> thinking about the next release in the 2.6.x line. IMO we want to walk the
> balance between maintaining a reasonable release cadence and getting a good
> amount of high-quality fixes. The timeframe is a little tricky as the
> holidays are approaching. If we have enough fixes accumulated in
> branch-2.6, some time early December might be a good target for cutting the
> first release candidate. Once we miss that window, I think we are looking
> at next January. I'd like to hear your thoughts on this.
>
> It'd be good if someone can volunteer for the release manager for 2.6.3.
> I'd be happy to help out in any way I can. Thanks!
>
> Regards,
> Sangjin
>
> On Mon, Nov 2, 2015 at 11:45 AM, Vinod Vavilapalli <
> vino...@hortonworks.com>
> wrote:
>
> > Just to stress on the following, it is very important that any critical
> > bug-fixes that we push into 2.8.0 or even trunk, we should consider them
> > for 2.6.3 and 2.7.3 if it makes sense. This is the only way we can avoid
> > extremely long release cycles like that of 2.6.1.
> >
> > Also, to clarify a little, use Target-version if you want a discussion of
> > the backport, but if you do end up backporting patches after that, you
> > should set the fix-version to be 2.6.1.
> >
> > Thanks
> > +Vinod
> >
> >
> > > On Nov 2, 2015, at 11:29 AM, Sangjin Lee  wrote:
> > >
> > > As you may have seen, 2.6.2 is out
> > > . I have also retargeted
> > all
> > > open issues that were targeted for 2.6.2 to 2.6.3.
> > >
> > > Continuing the discussion in the email thread here
> > > , I'd like us to maintain
> > the
> > > cadence of monthly point releases in the 2.6.x line. It would be great
> if
> > > we can have 2.6.3 released before the year-end holidays.
> > >
> > > If you have any bugfixes and improvements that are targeted for 2.7.x
> (or
> > > 2.8) that you think are applicable to 2.6.x, please *set the target
> > version
> > > to 2.6.3* and merge them to branch-2.6. Please use your judgment in
> terms
> > > of the applicability and quality of the changes so that we can ensure
> > each
> > > point release is consistently better quality than the previous one.
> > Thanks
> > > everyone!
> > >
> > > Regards,
> > > Sangjin
> >
> >
>

Re: continuing releases on Apache Hadoop 2.6.x

[Sangjin Lee]

I'd like to pick up this email discussion again. It is time that we started
thinking about the next release in the 2.6.x line. IMO we want to walk the
balance between maintaining a reasonable release cadence and getting a good
amount of high-quality fixes. The timeframe is a little tricky as the
holidays are approaching. If we have enough fixes accumulated in
branch-2.6, some time early December might be a good target for cutting the
first release candidate. Once we miss that window, I think we are looking
at next January. I'd like to hear your thoughts on this.

It'd be good if someone can volunteer for the release manager for 2.6.3.
I'd be happy to help out in any way I can. Thanks!

Regards,
Sangjin

On Mon, Nov 2, 2015 at 11:45 AM, Vinod Vavilapalli 
wrote:

> Just to stress on the following, it is very important that any critical
> bug-fixes that we push into 2.8.0 or even trunk, we should consider them
> for 2.6.3 and 2.7.3 if it makes sense. This is the only way we can avoid
> extremely long release cycles like that of 2.6.1.
>
> Also, to clarify a little, use Target-version if you want a discussion of
> the backport, but if you do end up backporting patches after that, you
> should set the fix-version to be 2.6.1.
>
> Thanks
> +Vinod
>
>
> > On Nov 2, 2015, at 11:29 AM, Sangjin Lee  wrote:
> >
> > As you may have seen, 2.6.2 is out
> > . I have also retargeted
> all
> > open issues that were targeted for 2.6.2 to 2.6.3.
> >
> > Continuing the discussion in the email thread here
> > , I'd like us to maintain
> the
> > cadence of monthly point releases in the 2.6.x line. It would be great if
> > we can have 2.6.3 released before the year-end holidays.
> >
> > If you have any bugfixes and improvements that are targeted for 2.7.x (or
> > 2.8) that you think are applicable to 2.6.x, please *set the target
> version
> > to 2.6.3* and merge them to branch-2.6. Please use your judgment in terms
> > of the applicability and quality of the changes so that we can ensure
> each
> > point release is consistently better quality than the previous one.
> Thanks
> > everyone!
> >
> > Regards,
> > Sangjin
>
>

Re: continuing releases on Apache Hadoop 2.6.x

[Vinod Vavilapalli]

Just to stress on the following, it is very important that any critical 
bug-fixes that we push into 2.8.0 or even trunk, we should consider them for 
2.6.3 and 2.7.3 if it makes sense. This is the only way we can avoid extremely 
long release cycles like that of 2.6.1.

Also, to clarify a little, use Target-version if you want a discussion of the 
backport, but if you do end up backporting patches after that, you should set 
the fix-version to be 2.6.1.

Thanks
+Vinod


> On Nov 2, 2015, at 11:29 AM, Sangjin Lee  wrote:
> 
> As you may have seen, 2.6.2 is out
> . I have also retargeted all
> open issues that were targeted for 2.6.2 to 2.6.3.
> 
> Continuing the discussion in the email thread here
> , I'd like us to maintain the
> cadence of monthly point releases in the 2.6.x line. It would be great if
> we can have 2.6.3 released before the year-end holidays.
> 
> If you have any bugfixes and improvements that are targeted for 2.7.x (or
> 2.8) that you think are applicable to 2.6.x, please *set the target version
> to 2.6.3* and merge them to branch-2.6. Please use your judgment in terms
> of the applicability and quality of the changes so that we can ensure each
> point release is consistently better quality than the previous one. Thanks
> everyone!
> 
> Regards,
> Sangjin

continuing releases on Apache Hadoop 2.6.x

[Sangjin Lee]

As you may have seen, 2.6.2 is out
. I have also retargeted all
open issues that were targeted for 2.6.2 to 2.6.3.

Continuing the discussion in the email thread here
, I'd like us to maintain the
cadence of monthly point releases in the 2.6.x line. It would be great if
we can have 2.6.3 released before the year-end holidays.

If you have any bugfixes and improvements that are targeted for 2.7.x (or
2.8) that you think are applicable to 2.6.x, please *set the target version
to 2.6.3* and merge them to branch-2.6. Please use your judgment in terms
of the applicability and quality of the changes so that we can ensure each
point release is consistently better quality than the previous one. Thanks
everyone!

Regards,
Sangjin