hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2804) Formatable changes log as html
Date Tue, 11 Mar 2008 08:24:48 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577333#action_12577333

Enis Soztutar commented on HADOOP-2804:

Clearly +1. Should we add an anchor to each entry so that we can link to them later if needed?

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

View raw message