On Mon, Jul 29, 2019 at 8:07 AM Antoine Pitrou <anto...@python.org> wrote: > > > Le 26/07/2019 à 21:33, Wes McKinney a écrit : > > To summarize my understanding of the plan: > > > > 1. TWO VERSIONS: As of 1.0.0, we establish separate FORMAT and LIBRARY > > versions. Currently there is only a single version number. > > > > 2. SEMANTIC VERSIONING: We follow https://semver.org/ with regards to > > communicating library API changes. Given the project's pace of > > evolution, most releases are likely to be MAJOR releases according to > > SemVer principles. > > > > 3. RELEASES: Releases of the project will be named according to the > > LIBRARY version. A major release may or may not change the FORMAT > > version. When a LIBRARY version has been released for a new FORMAT > > version, the latter is considered to be released and official. > > > > 4. Each LIBRARY version will have a corresponding FORMAT version. For > > example, LIBRARY versions 2.0.0 and 3.0.0 may track FORMAT version > > 1.0.0. The idea is that FORMAT version will change less often than > > LIBRARY version. > > Will a new supported FORMAT version always bump the LIBRARY to the next > MAJOR version? >
Yes > > 5. BACKWARD COMPATIBILITY GUARANTEE: A newer versioned client library > > will be able to read any data and metadata produced by an older client > > library. > > Should this be "starting from 1.0.0"? Did we have some format-breaking > changes before? > Implicitly this entire list of statements is starting with 1.0.0 And yes we did, see https://github.com/apache/arrow/blob/master/format/Schema.fbs#L22 > Regards > > Antoine.
