Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <12578298.1185924232924.JavaMail.jira@brutus>
Date: Tue, 31 Jul 2007 16:23:52 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1667) organize CHANGES.txt messages into
 sections for future releases
In-Reply-To: <2154558.1185920332818.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516821 ] 

dhruba borthakur commented on HADOOP-1667:
------------------------------------------

Can you pl clarify what is an INCOMPATIBLE change? For example, is a change in ClientProtocol an incompatible change?

> organize CHANGES.txt messages into sections for future releases
> ---------------------------------------------------------------
>
>                 Key: HADOOP-1667
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1667
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 0.15.0
>
>         Attachments: changes.patch
>
>
> The entries in CHANGES.txt should have the following sections per release:
> INCOMPATIBLE CHANGES
> NEW FEATURES
> OPTIMIZATIONS
> BUG FIXES
> This should make it easier for folks to read this file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.