Update developer guide and define versioning strategy

Author: TrafalgarZZZ

.github/workflows/release.yml

@@ -4,7 +4,7 @@ on:
   push:
     tags:
       - v[0-9]+.[0-9]+.[0-9]+
-      - v[0-9]+.[0-9]+.[0-9]+.alpha[0-9]+
+      - v[0-9]+.[0-9]+.[0-9]+.post[0-9]+
       - v[0-9]+.[0-9]+.[0-9]+-rc[0-9]+
 
 jobs:

README.md

@@ -103,6 +103,15 @@ if __name__ == '__main__':
     main()
 ```
 
+## Versioning
+
+Fluid Python SDK's version **ALWAYS** follows the Fluid's version as long as they share the fully compatible APIs. For example, if a released version of Fluid is v1.0.1, Fluid Python SDK with version prefix "v1.0.1" is guaranteed to have 
+same APIs as the released Fluid version. 
+
+Fluid Python SDK may have "post" version that updates the inner code but keep the APIs untouched (e.g. hotfixes). For example, "v1.0.1.post1" is a post version of "v1.0.1" which includes the latest
+changes.
+
+
 ## Documentation For Models
 
  - [APIGatewayStatus](docs/APIGatewayStatus.md)

fluid/__init__.py

@@ -13,7 +13,7 @@
 
 from __future__ import absolute_import
 
-__version__ = "0.1.2"
+__version__ = "1.0.2"
 
 # import apis into sdk package
 

hack/develop/developer_guide.md

@@ -69,13 +69,18 @@ Now starts the Python interpreter and you can import the SDK:
 
 4. Cut a release and publish it to PyPi
 
-   Similarly, to cut a release and publish it to PyPi, tag the latest commit with `vX.Y.Z` and use `git push --tags` to
+   Similarly, to cut a release and publish it to PyPi, tag the latest commit with `vX.Y.Z` or `vX.Y.Z.postN`(See [Versioning](../../README.md#Versioning)) and use `git push --tags` to
    trigger
    a [GitHub Workflow](https://github.com/fluid-cloudnative/fluid-client-python/blob/master/.github/workflows/release.yml)
    to automatically build and publish the package to PyPi.
    For example:
     ```
+    # first release (compatible APIs with Fluid v1.0.1)
     git tag v1.0.1
+   
+    # second release (compatible APIs with Fluid v1.0.1)
+    git tag v1.0.1.post1
+   
     git push --tags origin
     ```