[
https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488117#comment-13488117
]
Josh Wills commented on CRUNCH-63:
----------------------------------
I think that having this becomes more important in the next release as we do
major surgery on the APIs and folks are going to need to know what went where.
My thought is that CHANGES.txt ends up being a selection of the most important
user-visible changes that go out with any release. The challenge here is that
it's somewhat subjective as to what qualifies as the "most important" changes--
maybe it's best that we leave it up to the release manager?
For 0.4.0, I think
1) The Scrunch REPL,
2) The addition of PObject,
3) Rahul's cleanup of o.a.c.test, and
4) The addition of crunch-contrib as a repo for code that doesn't fit into
examples/ and doesn't have any additional dependencies
are the most important changes.
> 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
