[
https://issues.apache.org/jira/browse/AVRO-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046675#comment-17046675
]
Elliotte Rusty Harold commented on AVRO-2687:
---------------------------------------------
Multi-language projects are certainly challenging. Beam experiences this as
well. Would it be possible to decouple the version numbers and release cycle
for different language libraries? Xerces does this, for example. Xerces Java is
a completely separate products from Xerces C++ and there's no confusion between
version numbers.
> Semantic Versioning
> -------------------
>
> Key: AVRO-2687
> URL: https://issues.apache.org/jira/browse/AVRO-2687
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> API level and other incompatibility between Avro minor versions is causing
> significant problems for Apache Beam. E.g.
> [https://github.com/apache/beam/pull/9779]
>
> Stable releases that don't break backwards compatibility would help us and
> other users a great deal. E.g. not removing joda.time support in 1.10.
>
> Absent that, at a minimum Avro should update its major version for any API
> breaking change. E.g. 1.9 should have been 2.0 because it was not API
> compatible with 1.8. In the case of Avro, this would apply not just to the
> public Java API but also to the serialization format.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
