aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSyoyo Fujita <syoyo@lighttransport.com>2021-08-27 20:11:30 +0900
committerSyoyo Fujita <syoyo@lighttransport.com>2021-08-27 20:11:30 +0900
commit3e401b55a4a9ebfc6344a8a2a698245e7d3fc09e (patch)
tree17f7e3d96e701250efe10e186e8833d9deae9ed8
parent8c089916e761858482df228ebdd2303a8a8b5671 (diff)
downloadtinyobjloader-3e401b55a4a9ebfc6344a8a2a698245e7d3fc09e.tar.gz
Update version tagging procedure for developers.
-rw-r--r--README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.md b/README.md
index 038e36c..143e042 100644
--- a/README.md
+++ b/README.md
@@ -421,7 +421,8 @@ cibuildwheels + twine upload for each git tagging event is handled in Azure Pipe
* Bump version in CMakeLists.txt
* Update version in `python/setup.py`
-* Commit with tag name starting with `v`(e.g. `v2.1.0`)
+* Commit and push `master`. Confirm C.I. build is OK.
+* Create tag starting with `v`(e.g. `v2.1.0`)
* `git push --tags`
* cibuildwheels + pypi upload(through twine) will be automatically triggered in Azure Pipeline.