hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@altiscale.com>
Subject Re: auto-generating changes.txt was: migrating private branches to the new git repo
Date Thu, 04 Sep 2014 02:10:20 GMT

I don't see HADOOP-10957 in hadoop-common-project/hadoop-cmmon/CHANGES.txt on github in the
2.5.1 branch.

On Sep 3, 2014, at 7:00 PM, Karthik Kambatla <kasha@cloudera.com> wrote:

> 2.5.1 - I believe all the commits here are in CHANGES.txt of 2.5.1. Which
> one is missing?
> 
> 
> On Wed, Sep 3, 2014 at 6:51 PM, Allen Wittenauer <aw@altiscale.com> wrote:
> 
>> Nothing official or clean or whatever, but just to give people an idea of
>> what an auto generated CHANGES.txt file might look like, here are some
>> sample runs of the hacky thing I built, based upon the fixVersion
>> information.  It doesn't break it down by improvement, etc.  Also, the name
>> on the end is the person who the JIRA is assigned.  If it is unassigned,
>> then it comes out blank.  It's interesting to note that in the 2.5.1 notes,
>> it does appear to have caught a commit missing from the changes.txt….
>> 
>> 2.5.1: http://pastebin.com/jXfz5wXz
>> 
>> 2.6.0: http://pastebin.com/5nkSsU18
>> 
>> 3.0.0: http://pastebin.com/3Ek4tP8d
>> 
>> One thing I didn't do was append the previous versions onto these files,
>> which is what I'd expect to happen.


Mime
View raw message