[
https://issues.apache.org/jira/browse/AVRO-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046689#comment-17046689
]
Ismaël Mejía edited comment on AVRO-2687 at 2/27/20 2:42 PM:
-------------------------------------------------------------
Well that seems like a lot of work for probably a similar output because then
users will doubt, wait is Python Avro 3.1.0 compatible with Java Avro 5.2.0?
and they will probably be for the binary format.
I think the best we can do at least for the moment is to add a clear message
about how current Avro versioning works in the website: MAJOR = Binary format
version MINOR = MAJOR in semver and PATCH = MINOR in semver
Notice that this is at least in principle but so far we have never moved a
MAJOR number because of some breaking API change in any language, so it is like
a 'best effort' semver
was (Author: iemejia):
Well that seems like a lot of work for probably a similar output because then
users will doubt, wait is Python Avro 3.1.0 compatible with Java Avro 5.2.0?
and they will probably be for the binary format.
I think the best we can do at least for the moment is to add a clear message
about how current Avro versioning works in the website: MAJOR = Binary format
version MINOR = MAJOR in semver and PATCH = MINOR in semver
> 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)
