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

Posted to dev@bigtop.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2011/08/09 00:32:27 UTC

[jira] [Created] (BIGTOP-14) Add CHANGES.txt generation to Makefile

Add CHANGES.txt generation to Makefile
--------------------------------------

                 Key: BIGTOP-14
                 URL: https://issues.apache.org/jira/browse/BIGTOP-14
             Project: Bigtop
          Issue Type: Task
          Components: General
            Reporter: Andrew Bayer
            Assignee: Andrew Bayer
             Fix For: 0.1.0


Add a target to the Makefile which will generate a usefully formatted CHANGES.txt. This will probably require specifying the previous release's tag in bigtop.mk so we can find its revision and then do an svn log for changes since then, or for all changes if no previous release is defined.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (BIGTOP-14) Add CHANGES.txt generation to Makefile

Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/BIGTOP-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer resolved BIGTOP-14.
--------------------------------

    Resolution: Fixed

> Add CHANGES.txt generation to Makefile
> --------------------------------------
>
>                 Key: BIGTOP-14
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-14
>             Project: Bigtop
>          Issue Type: Task
>          Components: General
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 0.1.0
>
>         Attachments: CHANGES.txt
>
>
> Add a target to the Makefile which will generate a usefully formatted CHANGES.txt. This will probably require specifying the previous release's tag in bigtop.mk so we can find its revision and then do an svn log for changes since then, or for all changes if no previous release is defined.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (BIGTOP-14) Add CHANGES.txt generation to Makefile

Posted by "Edward J. Yoon (JIRA)" <ji...@apache.org>.

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

Edward J. Yoon commented on BIGTOP-14:
--------------------------------------

+1

> Add CHANGES.txt generation to Makefile
> --------------------------------------
>
>                 Key: BIGTOP-14
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-14
>             Project: Bigtop
>          Issue Type: Task
>          Components: General
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 0.1.0
>
>         Attachments: CHANGES.txt
>
>
> Add a target to the Makefile which will generate a usefully formatted CHANGES.txt. This will probably require specifying the previous release's tag in bigtop.mk so we can find its revision and then do an svn log for changes since then, or for all changes if no previous release is defined.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (BIGTOP-14) Add CHANGES.txt generation to Makefile

Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/BIGTOP-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer updated BIGTOP-14:
-------------------------------

    Attachment: CHANGES.txt

Ok, decided not to go with automatic CHANGES.txt generation for now. So here's an initial CHANGES.txt file.

> Add CHANGES.txt generation to Makefile
> --------------------------------------
>
>                 Key: BIGTOP-14
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-14
>             Project: Bigtop
>          Issue Type: Task
>          Components: General
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 0.1.0
>
>         Attachments: CHANGES.txt
>
>
> Add a target to the Makefile which will generate a usefully formatted CHANGES.txt. This will probably require specifying the previous release's tag in bigtop.mk so we can find its revision and then do an svn log for changes since then, or for all changes if no previous release is defined.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira