[
https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488084#comment-13488084
]
Gabriel Reid commented on CRUNCH-63:
------------------------------------
So then the question is: do we want to just focus on writing better JIRA
summaries (or at least cleaning them up before release) and include the
information in the repo, or just try to improve the information in JIRA without
worrying about including the file.
I just took a look at what Avro does (as that's the project that I generally
follow the changes most in) and it looks like they do indeed include a dump
from JIRA in their repo. I don't find this useful myself, as I always just
consult the release notes in JIRA. As far as I'm concerned, just having a link
to JIRA in our README will be sufficient to provide this information, but I can
understand that I may be the only one who feels that way.
> Add a CHANGES.txt
> -----------------
>
> Key: CRUNCH-63
> URL: https://issues.apache.org/jira/browse/CRUNCH-63
> Project: Crunch
> Issue Type: Task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> It will be useful to have a CHANGES.txt to clearly communicate new-features,
> incompatible changes, bug-fixes etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
