Merge pull request #16 from inloco/chore/readme-adds-deployment-section

chore(README.md): adds deployment section

README.md

@@ -198,8 +198,50 @@ Every method call can throw `IncogniaHTTPError` and `IncogniaError`.
 
 ## How to Contribute
 
-If you have found a bug or if you have a feature request, please report them at this repository
-issues section.
+Your contributions are highly appreciated. If you have found a bug or if you have a feature request,
+please report them at this repository
+[issues section](https://github.com/inloco/incognia-python/issues).
+
+### Development
+
+#### Versioning
+
+This project uses [Semantic Versioning](https://semver.org/), where version follows
+`v{MAJOR}.{MINOR}.{PATCH}` format. In summary:
+
+- _Major version update_ - Major functionality changes. Might not have direct backward
+  compatibility.
+  For example, multiple public API parameter changes.
+- _Minor version update_ - Additional features. Major bug fixes. Might have some minor backward
+  compatibility issues. For example, an extra parameter on a callback function.
+- _Patch version update_ - Minor features. Bug fixes. Full backward compatibility. For example,
+  extra fields added to the public structures with version bump.
+
+#### Release
+
+On GitHub, you should merge your changes to the `main` branch, create the git
+[versioning](#Versioning) tag and finally push those changes:
+
+```shell
+$ git checkout main
+$ git pull
+$ git merge <your_branch>
+$ git tag -a v<version> -m "<description>"
+$ git push origin HEAD --tags
+```
+
+- example:
+
+```shell
+$ git checkout main
+$ git pull
+$ git merge feat/some-feature
+$ git tag -a v2.1.0 -m "This release adds some feature..."
+$ git push origin HEAD --tags
+```
+
+Our CI will build images with the tagged version and publish them
+to [our PyPI repository](https://pypi.org/project/incognia-python/).
 
 ## What is Incognia?