hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12285) Reorganize test-patch footer table
Date Wed, 23 Sep 2015 05:11:05 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Busbey updated HADOOP-12285:
---------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: HADOOP-12111)

> Reorganize test-patch footer table
> ----------------------------------
>
>                 Key: HADOOP-12285
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12285
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: yetus
>            Reporter: Kengo Seki
>
> In response to: https://issues.apache.org/jira/browse/HADOOP-12266?focusedCommentId=14647672&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14647672
> {quote}
> * when further information is needed, we often publish that in the footer as well, and
having all of these versions published in the footer makes those hard to find
> * are we better off actually adding a fourth table just for versions and other operating
information? or just exercising better control over the footer table to force versions lower
than logs? in code, versions could be in a separate table but in display one table
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message