[
https://issues.apache.org/jira/browse/AVRO-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762305#action_12762305
]
Jon Bratseth commented on AVRO-133:
-----------------------------------
There was some degree of confusion amongst those implementing the spec
in a meeting we had Friday because people were not aware of changes
which happened after they printed their copy, looked at it last or
whatever.
So, judging from empirical evidence, something more is needed :-)
At the very least I think there should be a minor in the version
number which is bumped each time there is a change, otherwise we'll
have implementations of "version 1.0" which are out of date with the
current "version 1.0".
A change log included in the document would also be convenient to
address cases as the above, it is nice with specs which are completely
standalone.
> The Avro spec must be change controlled
> ---------------------------------------
>
> Key: AVRO-133
> URL: https://issues.apache.org/jira/browse/AVRO-133
> Project: Avro
> Issue Type: Bug
> Components: spec
> Reporter: Jon Bratseth
>
> It seems currently changes are being made without bumping the version number.
> The spec should:
> - Change minor number each time any change is made
> - Include a change log listing each change and accompanying version number
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
