Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
MIME-Version: 1.0
From: Ajay Yadava <ajayyadava@apache.org>
Date: Thu, 21 Jan 2016 00:21:30 +0530
Message-ID: 
 <CAKCPnS7eW=wW5n5q1cYnJffy-Nz5KzTsKL02kNucE4M2yd1ozg@mail.gmail.com>
Subject: [DISCUSS] Removing CHANGES.txt
To: dev@falcon.apache.org
Content-Type: multipart/alternative; boundary=001a1144102a28b7b20529c87b83

--001a1144102a28b7b20529c87b83
Content-Type: text/plain; charset=UTF-8

Currently we are maintaining CHANGES.txt to record contributions,
 committers of the commits and the release in which they got committed. All
this information is also available in JIRA and git.

However, there are certain disadvantages of CHANGES.txt, every time during
release we have to maintain different CHANGES.txt in master and branch. We
have to be careful with subtle details like "Proposed release version" and
"Released version" etc. This also creates confusion when same commit gets
committed into master and the branch.

Also, it entails committers to do some edits to the patch submitted by the
contributor. This is error prone and can be tedious sometimes. Sometimes we
forget to attribute contribution or spell contributor's name incorrectly.

Hence I propose to delete CHANGES.txt from master (0.10 onward). Please
provide your inputs. If everyone agrees, then I will create a JIRA and
delete CHANGES.txt from master.


Cheers
Ajay Yadava

--001a1144102a28b7b20529c87b83--