[
https://issues.apache.org/jira/browse/HADOOP-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577666#action_12577666
]
Hadoop QA commented on HADOOP-2804:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377575/HADOOP-2804.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1941/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1941/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1941/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1941/console
This message is automatically generated.
> Formatable changes log as html
> ------------------------------
>
> Key: HADOOP-2804
> URL: https://issues.apache.org/jira/browse/HADOOP-2804
> Project: Hadoop Core
> Issue Type: Improvement
> Components: documentation
> Reporter: Nigel Daley
> Assignee: Nigel Daley
> Priority: Minor
> Fix For: 0.17.0
>
> Attachments: changes.html, ChangesFancyStyle.css,
> ChangesSimpleStyle.css, HADOOP-2804.patch, HADOOP-2804.patch
>
>
> We could do a better job of generating useful release notes. As a first
> step, I suggest we follow Lucene's lead and add html formatting to our
> CHANGES.txt. An example output is here:
> http://hudson.zones.apache.org/hudson/view/Lucene/job/Lucene-trunk/lastSuccessfulBuild/artifact/trunk/build/docs/changes/Changes.html
> This should then be included with our release documentation that is published
> on the website for each release.
> After this is committed, the next step is for committers to agree on a
> CHANGES.txt convention that will flag major features/improvements (such as a
> well placed *). Then the flagged Jira's can be further highlighted when
> generating the html.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
