hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: auto-generating changes.txt was: migrating private branches to the new git repo
Date Thu, 04 Sep 2014 11:38:30 GMT
is there any way of isolating compatible/incompatible changes, & new
features?

I know that any change is potentially incompatible —but it is still good to
highlight the things we know are likely to cause trouble


On 4 September 2014 02:51, 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.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message