[
https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488142#comment-13488142
]
Matthias Friedrich commented on CRUNCH-63:
------------------------------------------
I agree that CHANGES.txt (without the .txt for consistency) works best as a
selection of the most important changes. I like the idea of cleaning up JIRA
summaries, too; best would be to fix them up when resolving an issue.
However, we're a relatively small team and not a TLP yet so I think we could
wait with publishing change logs, maybe until graduation. But I'm ok with
letting the RM decide even though he will implicitly make the decision for all
following releases :)
> 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
