[jira] [Created] (HADOOP-16519) Updating incompatible issue

xia0c created HADOOP-16519: -- Summary: Updating incompatible issue Key: HADOOP-16519 URL: https://issues.apache.org/jira/browse/HADOOP-16519 Project: Hadoop Common Issue Type: Bug Affects Version

[jira] [Created] (HADOOP-16518) Updating incompatible issue

xia0c created HADOOP-16518: -- Summary: Updating incompatible issue Key: HADOOP-16518 URL: https://issues.apache.org/jira/browse/HADOOP-16518 Project: Hadoop Common Issue Type: Bug Component

Re: [DISCUSS] Hadoop 2019 Release Planning

Thanks Wangda for bring this up! I ran the submarine 0.2.0 release before with a lot of help from folks especially Sunil. :D And this time I would like to help to release the 3.1.4. Thanks! BR, Zhankun Hui Fei 于2019年8月16日 周五下午7:19写道： > Hi Wangda, > Thanks for bringing this up! > Looking forward

Re: [DISCUSS] Hadoop 2019 Release Planning

Hi Wangda, Thanks for bringing this up! Looking forward to see HDFS 3.x is widely used，but RollingUpgrade is a problem. Hope commiters watch and review these issues, Thanks https://issues.apache.org/jira/browse/HDFS-13596 https://issues.apache.org/jira/browse/HDFS-14396 Wangda Tan 于2019年8月10日周六 上

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/415/ [Aug 15, 2019 2:21:17 AM] (iwasakims) HDFS-14707. Add JAVA_LIBRARY_PATH to HTTPFS startup options in branch-2. -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen

Make EOL branches to public?

Hi folks, Want to hear your thoughts about what we should do to make some branches EOL. We discussed a couple of times before in dev lists and PMC list. However, we couldn't get a formal process of EOL. According to the discussion. It is hard to decide it based on time like "After 1st release, EOL

Re: [DISCUSS] Hadoop 2019 Release Planning

Thanks all for the discussion, - I'd like the volunteered release managers to review this issue: https://issues.apache.org/jira/browse/HADOOP-16494 - I can co-RM for a release. Thanks and regards, Akira On Fri, Aug 16, 2019 at 6:49 PM Wangda Tan wrote: > > Thanks all for the suggestions and vol

Re: [DISCUSS] Hadoop 2019 Release Planning

Thanks all for the suggestions and volunteering run these releases: I just updated roadmap of Hadoop wiki: https://cwiki.apache.org/confluence/display/HADOOP/Roadmap Now I put 5 releases and planned date is 2019. We have 3 releases have volunteered RM (Release Manager): - 3.2.1: Rohith - 2.8.6:

Re: Thoughts about moving submarine to a separate git repo?

+1 ，Agree that independent development of submarine can better adapt to the development of machine learning dashuiguailu...@gmail.com From: Xun Liu Date: 2019-08-16 12:43 To: common-dev; yarn-dev; hdfs-dev; submarine-dev Subject: Thoughts about moving submarine to a separate git repo? Dear Su

Re: [DISCUSS] Hadoop 2019 Release Planning

Hi Wangda, Thanks for initiating this. I would like to nominate myself for 3.2.1 Release Management. -Rohith Sharma K S On Sat, 10 Aug 2019 at 08:29, Wangda Tan wrote: > Hi all, > > Hope this email finds you well > > I want to hear your thoughts about what should be the release plan for > 2019

Re: Thoughts about moving submarine to a separate git repo?

Hi Xun, Thanks for the proposal. Altogether this proposal makes sense to me. IIUC, an external repo is created and developers found more productive in that because of faster reviews and commits. To do more this apache way, 1. I think its better we track all this in apache jira (apparently this is