You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2008/03/11 05:12:46 UTC

[jira] Updated: (HADOOP-2804) Formatable changes log as html

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

Nigel Daley updated HADOOP-2804:
--------------------------------

    Attachment: HADOOP-2804.patch

Updated patch to remove the need for changes.xml

> 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.