-
Notifications
You must be signed in to change notification settings - Fork 41
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
How to deal with minimal model updates #169
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the description in the versioning process we should adhere to the semver standard.
Thanks for the comments. Models don't really have an "API", they are the foundation for generation of an API. I've added a reference but and wrote more precise criteria for what change consitutes what increment |
From discussion: legal requirements are probably no minor change but major, eg change of copyright header |
Removing or adding optional elements is not a minor change as it implies a breaking change -> important add for item "minor changes" that backward compatibility needs to be maintained |
@arnoweiss have you had a chance to adjust according to our previous discussion? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change reflects the result of the discussion and can be merged
Description
This PR amends the governance process with regard to how semantic versioning shall be interpreted in the scope of this project.
Closes #130