Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strategy for versioning #103

Open
havogt opened this issue Dec 5, 2017 · 2 comments
Open

Strategy for versioning #103

havogt opened this issue Dec 5, 2017 · 2 comments
Milestone

Comments

@havogt
Copy link
Collaborator

havogt commented Dec 5, 2017

Currently we pretend to be backwards compatible, i.e. a new serialbox version will read an archive from an earlier version. (This was changed recently, before it was a requirement to have the same version for writing and reading.)

Probably the patch version should be backwards compatible i.e. 2.1.x
but minor version should be incompatible 2.x.0.

@havogt
Copy link
Collaborator Author

havogt commented Aug 21, 2018

I think we should introduce a separate version for archives, i.e. we only increase the archive version number if something changed in the archive. Then again the same question as above for this version number.
See also #151

@havogt havogt added this to the v3.0.0 milestone Mar 26, 2019
@clementval
Copy link
Collaborator

I faced the problem again today! This is really crazy to check even patch number for archive compatibility.

Serialbox: ERROR: error while parsing "./ser_data/MetaData-current_jsb_ser_rank0.json": serialbox version of MetaData (2.4.3) does not match the version of the library (2.4.2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants