Hi Eric,
> If we're not using patches on JIRA anymore, why are we using JIRA at all?
JIRA issues contain useful information in the fields. We are leveraging
them in development and release process.
> Using JIRA to then redirect to GitHub seems unintuitive and will fracture
the information betwee
tomscut created HDFS-16527:
--
Summary: Add global timeout rule for TestRouterDistCpProcedure
Key: HDFS-16527
URL: https://issues.apache.org/jira/browse/HDFS-16527
Project: Hadoop HDFS
Issue Type: Imp
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/280/
[Mar 29, 2022 7:58:27 AM] (gyorandr) YARN-10549. Decouple RM runner logic from
SLSRunner. Contributed by Szilard Nemeth.
[Mar 29, 2022 3:44:55 PM] (noreply) HDFS-16523. Fix dependency error in
hadoo
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/825/
[Mar 30, 2022 6:56:04 AM] (Xiaoqiao He) HDFS-16498. Fix NPE for
checkBlockReportLease #4057. Contributed by tomscut.
[Mar 30, 2022 11:42:50 AM] (noreply) HADOOP-18145. Fileutil's unzip method
causes
I think this deserves some attention. More than just the question of JIRA
vs GitHub Issues, I'm a little concerned that we completely changed the way
we post code changes without a vote thread or even a discussion thread that
had a clear outcome. The previous thread ([DISCUSS] Tips for improving
pr
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/617/
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
