[VOTE] Release Apache Hadoop 3.3.1 RC2

Hi community, This is the release candidate RC2 of Apache Hadoop 3.3.1 line. All blocker issues have been resolved [1] again. There are 4 issues resolved for RC2: * HADOOP-17666. Update LICENSE for 3.3.1 * MAPREDUCE-7348. TestFrameworkUploader#testNativeIO fails. (#3053) * Revert "HADOOP-17563. U

Re: [VOTE] Release Apache Hadoop 3.3.1 RC2

Cancelling RC2. @Ayush Saxena found an issue HADOOP-16878 which we need to revert. I'll work on the RC3 asap. On Tue, Jun 1, 2021 at 3:23 PM Wei-Chiu Chuang wrote: > Hi community, > > This is the release candidate RC2 of Apache Hadoop 3.3.1

[VOTE] Release Apache Hadoop 3.3.1 RC3

Hi community, This is the release candidate RC3 of Apache Hadoop 3.3.1 line. All blocker issues have been resolved [1] again. There are 2 additional issues resolved for RC3: * Revert "MAPREDUCE-7303. Fix TestJobResourceUploader failures after HADOOP-16878 * Revert "HADOOP-16878. FileUtil.copy() t

[jira] [Created] (HADOOP-17741) RPC authentication based on user and IP

Xiangyi Zhu created HADOOP-17741: Summary: RPC authentication based on user and IP Key: HADOOP-17741 URL: https://issues.apache.org/jira/browse/HADOOP-17741 Project: Hadoop Common Issue Type:

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/525/ [May 31, 2021 8:43:26 PM] (noreply) HADOOP-17735. Upgrade AWS SDK to 1.11.1026 (#3057) -1 overall The following subsystems voted -1: blanks pathlen unit xml The following subsystems voted

Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/317/ No changes -1 overall The following subsystems voted -1: asflicense hadolint mvnsite pathlen unit The following subsystems voted -1 but were configured to be filtered/ignored: cc

Apache Hadoop qbt Report: trunk+JDK11 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/178/ [May 31, 2021 8:43:26 PM] (noreply) HADOOP-17735. Upgrade AWS SDK to 1.11.1026 (#3057) [Jun 1, 2021 3:04:56 AM] (Ayush Saxena) HDFS-16051. Misspelt words in DataXceiver.java line 881 and line 885. C

Do I need a +1 to merge a backport PR?

I'm curious about the GitHub PR conventions we use today... say I want to backport a commit from trunk to branch-3.3, and there's a small code conflict so I push a PR against branch-3.3 using GitHub to go through the precommit check. Do I need explicit approval from another committer to merge the

Re: Do I need a +1 to merge a backport PR?

I think we usually merge backport without explicit +1 if the conflict is trivial, same as done on JIRA-only workflow (on which we attached patch like HADOOP-xxx-branch-3.3.001.patch for precommit check then commit it without explicit +1). If committers want review since the change is not trivial

[jira] [Resolved] (HADOOP-17008) Release Hadoop 3.3.0

[ https://issues.apache.org/jira/browse/HADOOP-17008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HADOOP-17008. -- Resolution: Done > Release Hadoop 3.3.0 > > > Ke