[
https://issues.apache.org/jira/browse/CRUNCH-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045835#comment-14045835
]
Gabriel Reid commented on CRUNCH-430:
-------------------------------------
I think it's worth thinking about how much we want to worry about binary
compatibility between releases. Obviously it's a good thing where possible, but
I don't think it should be getting in the way of general improvements too much
either.
What I'm thinking is that maybe 0.8.3 should strive to be binary compatible
with 0.8.2, etc, but that this maybe isn't needed for going from 0.9 to 0.10.
At the very least I think it would be a good idea to mark the reinstated
methods as deprecated, which gives us a bit more of an excuse to git rid of
them in a couple of releases from now. It might also be interesting to consider
only reinstating these methods in the 0.8 branch.
> Re-add avroFile(AvroType) methods to From/At
> --------------------------------------------
>
> Key: CRUNCH-430
> URL: https://issues.apache.org/jira/browse/CRUNCH-430
> Project: Crunch
> Issue Type: Bug
> Affects Versions: 0.10.0, 0.8.3
> Reporter: Josh Wills
> Fix For: 0.8.4, 0.11.0
>
> Attachments: CRUNCH-430.patch
>
>
> In the interest of preserving binary compatability with the 0.8.2/0.9.0 code
> bases, we should keep the avroFile(AvroType) methods that were replaced with
> the avroFile(PType) methods in CRUNCH-406.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
