[
https://issues.apache.org/jira/browse/HDFS-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475338#comment-16475338
]
Chris Douglas commented on HDFS-12615:
--------------------------------------
bq. Could you please do me a favor and move all future work and all the JIRAs
not released into a branch?
"All future work" is too broad, but developing complex features in branches is
a fair ask. Would you mind looking through the JIRAs implementing quotas and
multi-subcluster mounts, as an exercise? Reasonable people can disagree on
minimum criteria requiring a feature branch, but calling a merge vote for 5-9
patches is probably excessive.
It is important to distinguish between routine maintenance and significant
features. For the latter, design docs should be written, experts' opinion
solicited, and implementation should be in a branch if it requires more than a
handful of patches. The project can't claim that RBF is secure, then issue a
flurry of CVEs that could have been caught in design review. In that particular
case, I assume the patch was shared for discussion, not commit.
bq. As I said, I feel bad the way this project is handled, that is heaping lots
of critical features without even design documents and all these features going
directly into the trunk.
[~anu], you should look at the code/JIRAs if you're going to make sweeping
statements like this. Many features did have design documents. Most JIRAs were
repairs/improvements to released functionality or straightforward extensions.
The only data point you've cited is the number of subtasks in this JIRA, which
is a clerical problem, not a stop-the-world emergency.
Since some subset of these JIRAs are already in a release, even that criterion
doesn't tie these JIRAs together. Your suggestion- moving JIRAs not part of a
release out of this umbrella- makes sense. Let's wrap up this issue as whatever
was released, then transition to (a) significant features in branches with
subtasks and (b) normal maintenance in individual JIRAs.
> Router-based HDFS federation phase 2
> ------------------------------------
>
> Key: HDFS-12615
> URL: https://issues.apache.org/jira/browse/HDFS-12615
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Labels: RBF
>
> This umbrella JIRA tracks set of improvements over the Router-based HDFS
> federation (HDFS-10467).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
