ami/tl-vikunja
1
0
Fork 0
Code

docs: clarify transitioning from unstable to release

Browse Source
This commit is contained in:
kolaente 2024-04-09 22:43:27 +02:00
parent bc19a2fb78
commit 0557d4b5bb
No known key found for this signature in database
GPG Key ID: F40E70337AB24C9B
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/content/doc/setup/versions.md
View File

@ -10,7 +10,7 @@ menu:
# Vikunja Versions # Vikunja Versions
The Vikunja api and frontend are available in two different release flavors. Vikunja api is available in two different release flavors.
{{< table_of_contents >}} {{< table_of_contents >}}
@ -30,6 +30,9 @@ There might be multiple new such builds a day.
Versions contain the last stable version, the number of commits since then and the commit the currently running binary was built from. Versions contain the last stable version, the number of commits since then and the commit the currently running binary was built from.
They look like this: `v0.18.1+269-5cc4927b9e` They look like this: `v0.18.1+269-5cc4927b9e`
Since a release is also cut from the main branch at some point, features from unstable will eventually become available in stable releases.
At the point in time of a new version release, the unstable build is the same exact thing.
The demo instance at [try.vikunja.io](https://try.vikunja.io) automatically updates and always runs the last unstable build. The demo instance at [try.vikunja.io](https://try.vikunja.io) automatically updates and always runs the last unstable build.
## Switching between versions ## Switching between versions