[
https://issues.apache.org/jira/browse/FALCON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated FALCON-2063:
--------------------------------
Summary: Add change log for 0.10 (was: Add change log for each release )
> Add change log for 0.10
> -----------------------
>
> 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)
