.apache.org"
; "mapreduce-dev@hadoop.apache.org"
; Vinod Kumar Vavilapalli
; Ming Ma
Sent: Wednesday, October 28, 2015 12:16 PM
Subject: Re: 2.7.2 release plan
I see you already put in both HDFS-8950 and HDFS-7725, so we are good there.
Can you please do a pass on HDFS-8871 an
> ; "hdfs-...@hadoop.apache.org"
> ; "mapreduce-dev@hadoop.apache.org"
> ; Vinod Kumar Vavilapalli
>
> Sent: Tuesday, October 27, 2015 2:39 AM
> Subject: Re: 2.7.2 release plan
>
> Vinod and Chris,
>
> Thanks for your reply. I'll do also
e.org"
; "hdfs-...@hadoop.apache.org"
; "mapreduce-dev@hadoop.apache.org"
; Vinod Kumar Vavilapalli
Sent: Tuesday, October 27, 2015 2:39 AM
Subject: Re: 2.7.2 release plan
Vinod and Chris,
Thanks for your reply. I'll do also backport not only bug fixes but
also do
Vinod and Chris,
Thanks for your reply. I'll do also backport not only bug fixes but
also documentations(I think 2.7.2 includes them). It helps users a lot.
Best,
- Tsuyoshi
On Tuesday, 27 October 2015, Vinod Vavilapalli
wrote:
> +1.
>
> Thanks
> +Vinod
>
> > On Jul 16, 2015, at 8:18 AM, Chris
+1.
Thanks
+Vinod
> On Jul 16, 2015, at 8:18 AM, Chris Nauroth wrote:
>
> I'd be comfortable with inclusion of any doc-only patch in minor releases.
> There is a lot of value to end users in pushing documentation fixes as
> quickly as possible, and they don't bear the same risk of regressions o
I'd be comfortable with inclusion of any doc-only patch in minor releases.
There is a lot of value to end users in pushing documentation fixes as
quickly as possible, and they don't bear the same risk of regressions or
incompatibilities as code changes.
--Chris Nauroth
On 7/16/15, 12:38 AM, "
Hi,
thank you for starting the discussion about 2.7.2 release.
> The focus obviously is to have blocker issues [2], bug-fixes and *no*
features / improvements.
I've committed YARN-3170, which is an improvement of documentation. I
thought documentation pages which can be fit into branch-2.7 can b
Thanks Vinod for starting 2.7.2 release plan.
> The focus obviously is to have blocker issues [2], bug-fixes and *no*
> features / improvements.
Can we adopt the plan as Karthik mentioned in "Additional maintenance
releases for Hadoop 2.y versions" thread? That way we can include not
only bloc
