[
https://issues.apache.org/jira/browse/HDFS-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330255#comment-14330255
]
Tsz Wo Nicholas Sze commented on HDFS-7769:
-------------------------------------------
> The ambiguity is whether ...
At least we agree that there is an ambiguity. I think no one care about the
ambiguity since, as [~shv] mentioned, HADOOP-8248 has been around for 3 years.
Why not clarify the bylaws?
> Requiring another committer to review also blocks development on "dead" areas
> of the codebase with only a single maintainer. Those either need to move out
> of the project or find new committers to help maintain it.
I did see in some cases that a committer asked a non-committer to post a patch
with some very detailed code advise, then acted as a reviewer and then
committed the patch. Or two or more committers blindly +1'ed on each others
patches, even patches with trivial problems. Not sure how to avoid these
problems.
Indeed, I hope that we could revise the bylaws, especially for the development
branch case. Does it count if a committer who has contributed to a development
branch +1 on the merge vote?
> TestHDFSCLI create files in hdfs project root dir
> -------------------------------------------------
>
> Key: HDFS-7769
> URL: https://issues.apache.org/jira/browse/HDFS-7769
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Trivial
> Fix For: 2.7.0
>
> Attachments: h7769_20150210.patch, h7769_20150210b.patch
>
>
> After running TestHDFSCLI, two files (data and .data.crc) remain in hdfs
> project root dir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
