Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 37226 invoked from network); 11 Mar 2008 08:26:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Mar 2008 08:26:17 -0000 Received: (qmail 13427 invoked by uid 500); 11 Mar 2008 08:26:13 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 13395 invoked by uid 500); 11 Mar 2008 08:26:13 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 13386 invoked by uid 99); 11 Mar 2008 08:26:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 01:26:12 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 08:25:44 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 93640234C092 for ; Tue, 11 Mar 2008 01:24:48 -0700 (PDT) Message-ID: <923228273.1205223888602.JavaMail.jira@brutus> Date: Tue, 11 Mar 2008 01:24:48 -0700 (PDT) From: "Enis Soztutar (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-2804) Formatable changes log as html In-Reply-To: <23607612.1202523367991.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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, 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.