Re: Planning Hadoop 2.6.1 release

2015-07-16 Thread Akira AJISAKA
Thanks Vinod for creating the list! @Akira, let’s sync up offline on how to take this forward in terms of the release process. Okay. Thanks, Akira On 7/16/15 10:24, Vinod Kumar Vavilapalli wrote: Alright, I’d like to make progress while the issue is hot. I created a label to discuss on

Re: [Test-Patch TLP] consensus on naming

2015-07-16 Thread Bruno P. Kinoshita
Hi Allen    Just to be clear:  yetus is about the layer between Jenkins and the unit tests.  Many Apache communities don’t bother looking at Jenkins and it’s reporting because a) it’s extremely noisy when you’re testing literally hundreds to thousands of patches a week (plus full builds!) and

[jira] [Created] (HADOOP-12241) Add specification of FileStatus

2015-07-16 Thread Masatake Iwasaki (JIRA)
Masatake Iwasaki created HADOOP-12241: - Summary: Add specification of FileStatus Key: HADOOP-12241 URL: https://issues.apache.org/jira/browse/HADOOP-12241 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-12242) Add TOC to filesystem.md

2015-07-16 Thread Masatake Iwasaki (JIRA)
Masatake Iwasaki created HADOOP-12242: - Summary: Add TOC to filesystem.md Key: HADOOP-12242 URL: https://issues.apache.org/jira/browse/HADOOP-12242 Project: Hadoop Common Issue Type:

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

2015-07-16 Thread Vinayakumar B
+1 for steve's suggestion. I agree completely that everything should be finalized before committing in. -Vinay On Jul 16, 2015 2:29 PM, Steve Loughran ste...@hortonworks.com wrote: 1. I agree that the bar for patches going in should be very high: there's always the risk of some subtle

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

2015-07-16 Thread Steve Loughran
1. I agree that the bar for patches going in should be very high: there's always the risk of some subtle regression. The more patches, the higher the risk, the more traumatic the update 2. I like the idea of having a list of proposed candidate patches, all of which can be reviewed and

Re: 2.7.2 release plan

2015-07-16 Thread Akira AJISAKA
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 blocker

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

2015-07-16 Thread Karthik Kambatla
On Thu, Jul 16, 2015 at 4:59 AM, Steve Loughran ste...@hortonworks.com wrote: 1. I agree that the bar for patches going in should be very high: there's always the risk of some subtle regression. The more patches, the higher the risk, the more traumatic the update 2. I like the idea of

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

2015-07-16 Thread Sean Busbey
On Thu, Jul 16, 2015 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: On Thu, Jul 16, 2015 at 4:59 AM, Steve Loughran ste...@hortonworks.com wrote: -any change to the signature of an API, including exception types text -changes to wire formats These two should hold for minor

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

2015-07-16 Thread Karthik Kambatla
On Thu, Jul 16, 2015 at 10:42 AM, Sean Busbey bus...@cloudera.com wrote: On Thu, Jul 16, 2015 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: On Thu, Jul 16, 2015 at 4:59 AM, Steve Loughran ste...@hortonworks.com wrote: -any change to the signature of an API, including

Re: [Test-Patch TLP] consensus on naming

2015-07-16 Thread Allen Wittenauer
On Jul 15, 2015, at 11:22 PM, Bruno P. Kinoshita brunodepau...@yahoo.com.br wrote: Good points. This layer between Jenkins and the unit tests seems useful. Thanks! We think so too! It’s why we’re working on pulling the code out of Hadoop to make it more generalized for

Re: 2.7.2 release plan

2015-07-16 Thread Chris Nauroth
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,

[jira] [Created] (HADOOP-12243) Grep command used in test-patch and smart-apply-patch should be GNU's one, not POSIX

2015-07-16 Thread Kengo Seki (JIRA)
Kengo Seki created HADOOP-12243: --- Summary: Grep command used in test-patch and smart-apply-patch should be GNU's one, not POSIX Key: HADOOP-12243 URL: https://issues.apache.org/jira/browse/HADOOP-12243

[jira] [Created] (HADOOP-12244) recover broken rebase?

2015-07-16 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-12244: - Summary: recover broken rebase? Key: HADOOP-12244 URL: https://issues.apache.org/jira/browse/HADOOP-12244 Project: Hadoop Common Issue Type:

[jira] [Reopened] (HADOOP-9882) Trunk doesn't compile

2015-07-16 Thread Mike Casile (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Casile reopened HADOOP-9882: - I now have an opposite-ish problem I think. I followed all of the directions, but now my protoc is

[jira] [Created] (HADOOP-12246) Apache Hadoop should be listed under big-data and hadoop categories

2015-07-16 Thread Ajoy Bhatia (JIRA)
Ajoy Bhatia created HADOOP-12246: Summary: Apache Hadoop should be listed under big-data and hadoop categories Key: HADOOP-12246 URL: https://issues.apache.org/jira/browse/HADOOP-12246 Project:

[jira] [Created] (HADOOP-12245) References to misspelled REMAINING_QUATA in FileSystemShell.md

2015-07-16 Thread Gera Shegalov (JIRA)
Gera Shegalov created HADOOP-12245: -- Summary: References to misspelled REMAINING_QUATA in FileSystemShell.md Key: HADOOP-12245 URL: https://issues.apache.org/jira/browse/HADOOP-12245 Project: Hadoop