Re: Stale PRs, practical advice

2025-08-08 Thread Dave Marion
FWIW, I'd be happy to do whatever is needed to get my 3 line change merged. I created two PRs for the two different branches in development at the time. It's stale because I was unable to get anyone to review it. https://issues.apache.org/jira/browse/HDFS-16864 On 2025/08/08 08:35:32 Xiaoqiao H

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

2025-08-08 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/2022/ [Aug 5, 2025, 10:29:57 PM] (Chris Nauroth) HDFS-12431. [JDK17] Upgrade JUnit from 4 to 5 in hadoop-hdfs Part10. [Aug 6, 2025, 1:42:33 AM] (github) HADOOP-19617 - [JDK17] Remove JUnit4 Dependency - T

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

2025-08-08 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1841/ 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

Re: Stale PRs, practical advice

2025-08-08 Thread Xiaoqiao He
Thanks Rich and Ayush for launching this discussion again. I think the consensus then was that auto-closing abandoned PRs was a very > unfriendly thing to do. Maybe it is time to start another thread to discuss auto-closing stale or abandoned PRs. From my perspective, it is smooth to auto-closin