You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (Jira)" <ji...@apache.org> on 2020/09/21 21:42:00 UTC
[jira] [Commented] (YETUS-32) Reorganize test-patch footer table
[ https://issues.apache.org/jira/browse/YETUS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199681#comment-17199681 ]
Allen Wittenauer commented on YETUS-32:
---------------------------------------
YETUS-995 may clean this up in a satisfactory manner. Linking.
> Reorganize test-patch footer table
> ----------------------------------
>
> Key: YETUS-32
> URL: https://issues.apache.org/jira/browse/YETUS-32
> Project: Yetus
> Issue Type: Improvement
> Components: Precommit
> Reporter: Kengo Seki
> Priority: Major
>
> 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
(v8.3.4#803005)