Hi Wes,
Le 07/06/2019 à 17:42, Wes McKinney a écrit : > > I think > this would have a lot of benefits for project onlookers to remove > various warnings around the codebase around stability and cautions > against persistence of protocol data. It's fair to say that if we _do_ > make changes in the future, that there will be a transition path for > migrate persisted data, should it ever come to that. I think that's a good idea, but perhaps the stability promise shouldn't cover the Flight protocol yet? > I would suggest a "1.0.0" release either as our next release (instead > of 0.14.0) or the release right after that (if we need more time to > get affairs in order), with the guidance for users of: I think we should first do a regular 0.14.0 with all that's on our plate right now, then work towards a 1.0.0 as the release following that. > PROTOCOL VERSION (1): Protocol version, so libraries bearing 1.x.y > will be forward and backwards compatible (though new metadata fields > introduced in newer versions will be dropped in older readers) > MAJOR VERSION (0): API changes possible (and indeed, likely) from > major release to major release > MINOR VERSION (0): No API changes, bug fix only release > > Thoughts on the above? That sounds reasonable to me. Regards Antoine.
