-
Notifications
You must be signed in to change notification settings - Fork 72
Bump version to 0.3.0 #2059
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
Bump version to 0.3.0 #2059
Conversation
❌ 148 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Why do we bump so quick? |
+1 ... we will hit 1.0 quickly at this rate. I am referring to the delta in the version number (not the frequency of updated versions). |
My current thinking is that we can follow semantic versioning (ref: https://semver.org/) more closely, given that the versioning isn't as big for branding onnxscript as for onnx and pytorch. (aka we can bump major versions with less constraints). The minor version happens when new apis/features are introduced, in this case opset22. We don't need to hit 1.0 if we don't want to. I.e. it will become 0.11, 0.12 etc. The patch versions are reserved for simple bug fixes that don't impact apis etc. |
Also for bug fixes we can branch out, change version numbers, and cherry pick like how onnx and pytorch do it. The VERISON number in the main branch is always bumped to the next minor version number after release. |
@titaiwangms ptal |
No description provided.