-
Notifications
You must be signed in to change notification settings - Fork 64
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
schema: reduce version number #1300
schema: reduce version number #1300
Conversation
Do we need to change the version numbers for the files in tests as well? |
I think the tests need to be updated accordingly. (There is still a version 3.0.0, so I wonder if we even do testing …) |
testing was stopped quite a while ago but it still sits there to keep nagging that we should do test ;-) |
updating them of, course would be good |
Why not leave away the |
@bwbohl I think it is better to go in two steps. First consolidate all the version numbers to 5.0-dev (which allows testing properly since it points to dev version), and then change to 5.0 for the release. |
This PR is a first step towards v5.0 as it reduces the current version number to two levels (
5.0-dev
).Fixes #1174