mirror of
https://github.com/ynput/ayon-core.git
synced 2025-12-25 05:14:40 +01:00
Versionning Openpype documentation
This commit is contained in:
parent
ce3d7a23a4
commit
30c2e82a0a
1 changed files with 15 additions and 1 deletions
|
|
@ -63,4 +63,18 @@ You can run OpenPype with `--use-staging` argument to add use staging versions.
|
|||
|
||||
:::note
|
||||
Running staging version is identified by orange **P** icon in system tray.
|
||||
:::
|
||||
:::
|
||||
|
||||
### OpenPype versionning
|
||||
|
||||
Openpype version control is based on sementic versioning
|
||||
|
||||
:::note
|
||||
The version of openpye is indicated by the variable `__version__` in the file `.\openpype\version.py`
|
||||
:::
|
||||
|
||||
For example OpenPype will consider the versions in this order: `3.8.0-nightly` < `3.8.0-nightly.1` < `3.8.0-rc.1` < `3.8.0` < `3.8.1-nightly.1` <`3.8.1` < `3.9.0` < `3.10.0` < `4.0.0`
|
||||
|
||||
See https://semver.org/ for more details
|
||||
|
||||
For studios customizing the source code of Openpype, it is recommended to build by adding a name and a number after the PATCH and not to deploy 3.8.0 from original OpenPype repositoy. For example, your builds will be `3.8.0-yourstudio.1` < `3.8.0-yourstudio.2` < `3.8.1-yourstudio.1`
|
||||
Loading…
Add table
Add a link
Reference in a new issue