-
Notifications
You must be signed in to change notification settings - Fork 1
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
Versioning Scheme #13
Comments
Reorganizing or reformatting a repository is a more disruptive change than Also, for data even more than code, it's important to adopt semver's
|
Makes sense. I was considering data values the files attempt to describe, but in reality, files changing at all will cause a host of problems for any programs computing on them. Let's try this again:
Indeed :) |
I think "metadata" is good as it stands. It means "data about the data". As It might do to an include an illustrative example or two, e.g. "adding, to
|
I like the "data semver", neat idea! |
In software, we've come to use things like semver to ensure programs and their dependencies interoperate well.
Problems with this:
Paths:
This is flexible to "whatever you want to do." This is liable to yield a proliferating mess of "version" schemes. This seems like the worst thing to do.
Are there well established (and sane) data versioning standards? I'm not too familiar with what's out there.
Discussion welcome.
The text was updated successfully, but these errors were encountered: