hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@hortonworks.com>
Subject Re: IMPORTANT: automatic changelog creation
Date Thu, 02 Apr 2015 19:40:05 GMT

We'd then doing two commits for every patch. Let's simply not remove CHANGES.txt from trunk,
keep the existing dev workflow, but doc the release process to remove CHANGES.txt in trunk
at the time of a release going out of trunk.


On Apr 2, 2015, at 10:12 AM, Allen Wittenauer <aw@altiscale.com<mailto:aw@altiscale.com>>

But in reality, I suspect the opposite: removing changes.txt just from trunk will make cherry
picks easier.  If you don’t have to update trunk’s changes.txt, you can cherry-pick with
no worries about conflict merges on changes.txt in other branches. Then just update changes.txt
in branch-2 manually as you would have done pre- this change anyway.

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