Change versioning scheme.

vezel-dev · Jun 17, 2021 · c49c7d1 · c49c7d1
1 parent 163640f
commit c49c7d1
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -10,4 +10,5 @@ used by other projects.
   `linux-arm64`, `osx-x64`, `win-x86`, etc.
 * Only the RIDs that are relevant to the .NET ecosystem will be covered (so e.g.
   `Zig.Toolset.linux-riscv64` will not be available).
-* The package version will match the official Zig release's version.
+* The package version will match the official Zig release's version, with an
+  extra fourth component added indicating the packaging version.
diff --git a/RELEASE.md b/RELEASE.md
@@ -3,9 +3,10 @@
 When a new Zig version is released, the process is as follows:
 
 * Update the `Version` property in
-  [`Directory.Build.props`](Directory.Build.props).
+  [`Directory.Build.props`](Directory.Build.props). Reset the fourth component
+  to zero.
 * Commit the change.
-* Tag a release as e.g. `v0.8.0`.
+* Tag a release as e.g. `v0.8.0.0`.
 * Push the commit and the tag.
 * Edit the draft release on GitHub to add a release note link, such as
   [this one](https://ziglang.org/download/0.8.0/release-notes.html).