From 30c2e82a0a52c5912147dbe09f12db5630de6b16 Mon Sep 17 00:00:00 2001 From: "clement.hector" Date: Tue, 22 Feb 2022 16:25:47 +0100 Subject: [PATCH 1/3] Versionning Openpype documentation --- website/docs/admin_distribute.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/website/docs/admin_distribute.md b/website/docs/admin_distribute.md index 9e9d21998d..af19cc9bff 100644 --- a/website/docs/admin_distribute.md +++ b/website/docs/admin_distribute.md @@ -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. -::: \ No newline at end of file +::: + +### 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` \ No newline at end of file From 1b23611c33cb36d22f7058c1b8601b9f35f85290 Mon Sep 17 00:00:00 2001 From: "clement.hector" Date: Tue, 22 Feb 2022 18:10:41 +0100 Subject: [PATCH 2/3] Fix BigRoy comment --- website/docs/admin_distribute.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/admin_distribute.md b/website/docs/admin_distribute.md index af19cc9bff..b7cb1a3cf7 100644 --- a/website/docs/admin_distribute.md +++ b/website/docs/admin_distribute.md @@ -65,16 +65,16 @@ You can run OpenPype with `--use-staging` argument to add use staging versions. Running staging version is identified by orange **P** icon in system tray. ::: -### OpenPype versionning +### OpenPype versioning -Openpype version control is based on sementic versioning +OpenPype version control is based on semantic versioning :::note -The version of openpye is indicated by the variable `__version__` in the file `.\openpype\version.py` +The version of OpenPype 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` \ No newline at end of file +For studios customizing the source code of OpenPype, a practical approach could be to build by adding a name and a number after the PATCH and not to deploy 3.8.0 from original OpenPype repository. For example, your builds will be: `3.8.0-yourstudio.1` < `3.8.0-yourstudio.2` < `3.8.1-yourstudio.1` \ No newline at end of file From 101d5bcb9b87d1ac91759c61ad28aa8661e6e2f7 Mon Sep 17 00:00:00 2001 From: "clement.hector" Date: Wed, 23 Feb 2022 10:21:37 +0100 Subject: [PATCH 3/3] end the sentences with a period --- website/docs/admin_distribute.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/admin_distribute.md b/website/docs/admin_distribute.md index b7cb1a3cf7..2cccce0fbd 100644 --- a/website/docs/admin_distribute.md +++ b/website/docs/admin_distribute.md @@ -67,14 +67,14 @@ Running staging version is identified by orange **P** icon in system tray. ### OpenPype versioning -OpenPype version control is based on semantic versioning +OpenPype version control is based on semantic versioning. :::note -The version of OpenPype is indicated by the variable `__version__` in the file `.\openpype\version.py` +The version of OpenPype 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` +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 +See https://semver.org/ for more details. -For studios customizing the source code of OpenPype, a practical approach could be to build by adding a name and a number after the PATCH and not to deploy 3.8.0 from original OpenPype repository. For example, your builds will be: `3.8.0-yourstudio.1` < `3.8.0-yourstudio.2` < `3.8.1-yourstudio.1` \ No newline at end of file +For studios customizing the source code of OpenPype, a practical approach could be to build by adding a name and a number after the PATCH and not to deploy 3.8.0 from original OpenPype repository. For example, your builds will be: `3.8.0-yourstudio.1` < `3.8.0-yourstudio.2` < `3.8.1-yourstudio.1`. \ No newline at end of file