s 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?
+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?
>
: 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
ay, 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 bi
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
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
_
> 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
, 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
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.
+Vino
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
>>
-...@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 tha
: 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
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 wr
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
ho
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,
15 matches
Mail list logo
