falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-2063) Add change log for each release
Date Thu, 07 Jul 2016 18:33:11 GMT

    [ https://issues.apache.org/jira/browse/FALCON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366560#comment-15366560
] 

ASF GitHub Bot commented on FALCON-2063:
----------------------------------------

GitHub user ajayyadava opened a pull request:

    https://github.com/apache/falcon/pull/217

    FALCON-2063 Add change log for each release

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ajayyadava/falcon 2063

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/217.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #217
    
----
commit d7cb54e150f0234fb1cbe515e3b9761a364bb8f8
Author: Ajay Yadava <ajaynsit@gmail.com>
Date:   2016-07-07T18:31:52Z

    FALCON-2063 Add change log for each release

----


> Add change log for each release 
> --------------------------------
>
>                 Key: FALCON-2063
>                 URL: https://issues.apache.org/jira/browse/FALCON-2063
>             Project: Falcon
>          Issue Type: New Feature
>            Reporter: Ajay Yadava
>            Assignee: Ajay Yadava
>
> As per the discussion on the mailing list we had decided to deprecate manual additions
to CHANGES.txt and generate it automatically.
> I propose to use Apache YETUS for generating CHANGES and release notes and it has following
benefits.
> 1. Generating changes.txt from jira is much more flexible than from commit messages.
As I noted earlier also, commits can't be modified, so if a developer forgets to attach metadata
/ attaches wrong metadata then generating release notes will be incorrect.
> 2. Yetus provides nice markdown formatted change log with links to each issue. They are
easy to read and you can go to the jira by clicking through the github.
> 3. It can also automate the generation of release notes, if we add them to corresponding
JIRA.
> 4. We don't need to write / maintain and go through all the existing/future learning
that YETUS went through.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message