You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/02/05 13:38:39 UTC

[jira] [Commented] (FALCON-1820) Generate CHANGES.txt automatically

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

Pallavi Rao commented on FALCON-1820:
-------------------------------------

Two options to programmatically generate CHANGES.txt:
1. A script a la https://github.com/apache/spark/blob/master/dev/create-release/generate-changelist.py that generates the change log at release time for a given release. We can additionally, derive the classification (feature/bug/incompatible change) from JIRA details. Onus will be on committer to bulk verify and fix the classification in case of inaccuracies.

2. Update current falcon_merge_pr.py to update CHANGES.txt for every git push (or pr merge). Similar to what happens now. It will derive the classification of JIRA from JIRA details, committer can modify it (will be prompted) and the change line will be under the corresponding head. The commit will include CHANGES.txt.

Any preferences, anyone?

> Generate CHANGES.txt automatically
> ----------------------------------
>
>                 Key: FALCON-1820
>                 URL: https://issues.apache.org/jira/browse/FALCON-1820
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>
> Details here - https://www.mail-archive.com/dev@falcon.apache.org/msg10131.html



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