Skip to content

Commit d73816d

Browse files
author
Tom Hendrikx
authoredJun 12, 2019
Update release_process.md
Fix typo
1 parent 6e80943 commit d73816d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎release_process.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Release Process ##
22
To create a release there are a few steps you should follow:
3-
- We use [Semantic Versioning](https://semver.org/). If you're going to release a breaking change or a major new feature, do a minor version bump (x.y.z => x.y+1.z), otherwise do a patch version bump (x.y.z => x.y.z+1).
3+
- We use [Semantic Versioning](https://semver.org/). If you're going to release a breaking change or a major new feature, do a minor version bump (x.y.z => x.y+1.z). Otherwise, do a patch version bump (x.y.z => x.y.z+1).
44
- If you decide to do a minor version change, handle deprecations. See (Pending)DeprecationWarning subclasses in `error.py`.
55
- Update the version number in `version.py` and push this to master.
66
- Create a new tag with the new version number in the following way: `git tag v<major.minor.patch>`.

0 commit comments

Comments
 (0)
Please sign in to comment.