Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Sat, 16 Jul 2011 19:18:00 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: 
 <888698683.20258.1310843880044.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HADOOP-1684) Release notes point to browsable
 JIRA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J resolved HADOOP-1684.
-----------------------------

    Resolution: Not A Problem

Release notes are now being compiled and an editorial pass is made over them for every release as well. I believe these are at least 70% user friendly, having once been a beginner and read the release notes from 0.19 -> 0.20. The process is still done in the same way since, I believe.

I do not think this JIRA is valid anymore (may be cause of time, it was opened in '07 when nutch hosted hadoop's links).

Thus, Not-a-problem (anymore).

> Release notes point to browsable JIRA
> -------------------------------------
>
>                 Key: HADOOP-1684
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1684
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Marco Nicosia
>
> Currently, the web pages on lucene.apache.org/hadoop link "release notes" as a pointer to JIRA. http://issues.apache.org/jira/browse/HADOOP?report=com.atlassian.jira.plugin.system.project:changelog-panel
> The problem with this is that JIRA's really not very user-friendly. Most of the Hadoop JIRA tickets describe the underlying cause, not the user exposed symptoms, so users who are nsidering a new release (say, looking for API changes) can't make head or tails of half of the tickets without being familiar with Hadoop internals.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira