patcon/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Projects Releases Wiki Activity

Revise version notes

Browse Source
This commit is contained in:
decentral1se 2021-05-05 20:22:35 +02:00
parent a962233c9f
commit d187478d72
No known key found for this signature in database
GPG Key ID: 92DAD76BD9567B8A
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/packager-guide.md
View File

@ -9,8 +9,12 @@ the main `app` service in the `compose.yml` file. So, if you are deploying
`gitea/gitea:1.13.4` then the version of your Gitea app package version is `gitea/gitea:1.13.4` then the version of your Gitea app package version is
`1.13.4`. `1.13.4`.
However, most apps have underlying services like databases. When a new version Additionally, most apps have underlying services like databases and/or caches.
is published and available in the `compose.yml` but then `app` service version When a new version is published and available in the `compose.yml` we use the
has not changed, then we are using a `<version>~<revision>` syntax. So, if you `<version>_<revision>` syntax. So, if you are still on `1.13.4` for Gitea but
are still on `1.13.4` for Gitea but you have `mariadb:10.6` upgraded from you have `mariadb:10.6` upgraded from `mariadb:10.5` then the Gitea app package
`mariadb:10.5` then the Gitea app package version would be `1.13.4~1`. version would be `1.13.4_1`.
Our high level goals of app versioning on this project are not to invent a new
versioning system. Therefore, we try to follow the upstream versioning as much
as possible. This scheme is still a work in progress.