You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,12 +36,11 @@ Code Contribution Procedure
36
36
37
37
# Release Versioning
38
38
39
-
When incrementing a version and creating a release, follow [Semantic Versioning](https://packaging.python.org/en/latest/discussions/versioning/) (`major.minor.patch`) [^1]. In particular:
39
+
When incrementing a version and creating a release, follow a "right-shifted" versioning scheme similar to [vLLM Release Versioning](https://github.com/vllm-project/vllm/blob/main/RELEASE.md) (`major.minor.patch[.post1]`) [^1]. In particular:
40
40
41
-
* major increment signals incompatible API changes
42
-
* minor increment signals added functionality that is backwards-compatible (e.g. new kernels, new SM support, etc)
43
-
* patch increment signals backwards-compatible bug fixes (both for functional and performance issues)
41
+
*_major_ increment signals architectural milestone and/or when incompatible API changes are made, similar to PyTorch 2.0.
42
+
*_minor_ increment signals significant backwards-compatible new features
43
+
*_patch_ increment signals small backwards-compatible features (e.g. new kernels, new SM support, etc) and backwards-compatible bug fixes
44
+
*_post1_ is an optional suffix for a quick follow up release with just backwards-compatible bug fixes
44
45
45
-
Optionally, use post-releases (e.g., `X.Y.Z.post1`) for minor changes, like a documentation change.
46
-
47
-
[^1]: We have not followed this strictly through v0.2.14.post1. But after v0.2.14.post1, the versioning should follow SemVer.
46
+
[^1]: We have not followed this strictly through v0.4.0. But after v0.4.0, the versioning should follow this "right-shifted" versioning scheme.
0 commit comments