hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karthik Kambatla <ka...@cloudera.com>
Subject Re: IMPORTANT: automatic changelog creation
Date Thu, 02 Apr 2015 16:51:13 GMT
Thanks for driving this, Allen. Can't wait to see CHANGES.txt removed.


On Wed, Apr 1, 2015 at 6:09 PM, Allen Wittenauer <aw@altiscale.com> wrote:

> Hello everyone!
>         (to: and reply-to: set to common-dev, cc: the rest of ‘em, to
> concentrate the discussion)
>         HADOOP-11731 has just been committed to *trunk*.  This change does
> two things:
> a) Removes dev-support/relnotes.py
> b) Adds dev-support/releasedocmaker.py
>         releasedocmaker.py works as a replacement for both the release
> notes generation process as well as the CHANGES.TXT file.  As documented in
> BUILDING.TXT, running ‘mvn site -Preleasedocs’ will generate both the
> release notes and a change log for that release in markdown format based
> upon the FixVersion field in JIRA.  During the creation of the website,
> these files are then converted to HTML for use on the apache.org
> website.   The release notes file only contains incompatible changes and
> JIRA that specifically have release notes.  The changes file only has the
> data for that release.
>         This is obviously an incompatible change.  There is a good chance
> this code will not appear in branch-2.  There might be some additional
> fallout (esp since some folks write code against CHANGES.TXT) so I wanted
> to give everyone a heads up.
>         Also, I’ll be filing some additional JIRAs/doing some additional
> work to:
> a) remove CHANGES.TXT from trunk

Removing this from trunk makes it particularly hard to cherry-pick changes
from trunk to branch-2. I would gate this on the removal of CHANGES.txt on
branch-2 as well, at least until we have some non-future releases off

> b) pre-populate x amount of Hadoop 2.x release data into trunk so that the
> auto-indexer can pick it up
> c) update the HowToRelease information with, well, how to do releases
> based upon these new capabilities

There is a create-release script that likely needs updating.

>         Thanks!

Karthik Kambatla
Software Engineer, Cloudera Inc.

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