You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/09/16 18:27:08 UTC
[jira] [Created] (CRUNCH-63) Add a CHANGES.txt
Vinod Kumar Vavilapalli created CRUNCH-63:
---------------------------------------------
Summary: Add a CHANGES.txt
Key: CRUNCH-63
URL: https://issues.apache.org/jira/browse/CRUNCH-63
Project: Crunch
Issue Type: Bug
Reporter: 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
[jira] [Assigned] (CRUNCH-63) Add a CHANGES.txt
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli reassigned CRUNCH-63:
---------------------------------------------
Assignee: Vinod Kumar Vavilapalli
> Add a CHANGES.txt
> -----------------
>
> Key: CRUNCH-63
> URL: https://issues.apache.org/jira/browse/CRUNCH-63
> Project: Crunch
> Issue Type: Bug
> 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Matthias Friedrich (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Gabriel Reid (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Matthias Friedrich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487594#comment-13487594 ]
Matthias Friedrich commented on CRUNCH-63:
------------------------------------------
Hmm, I agree. Just dumping JIRA release notes into a text file isn't very helpful, we'd have to write far better JIRA summaries for this to work.
> 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Josh Wills (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Rahul Sharma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487593#comment-13487593 ]
Rahul Sharma commented on CRUNCH-63:
------------------------------------
Do we really want this file in our repo ? The same information is available in JIRA release notes, then why copy it ?
> 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
[jira] [Updated] (CRUNCH-63) Add a CHANGES.txt
Posted by "Matthias Friedrich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Friedrich updated CRUNCH-63:
-------------------------------------
Issue Type: Task (was: Bug)
Important, but not a bug :)
> 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
[jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Posted by "Josh Wills (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488149#comment-13488149 ]
Josh Wills commented on CRUNCH-63:
----------------------------------
Ha! That's a fair point. It seems like the feeling in the group is no CHANGES for now-- pun intended. :)
> 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