From 0557d4b5bba1a111ed70a484f88cec1636e29371 Mon Sep 17 00:00:00 2001 From: kolaente Date: Tue, 9 Apr 2024 22:43:27 +0200 Subject: [PATCH] docs: clarify transitioning from unstable to release --- docs/content/doc/setup/versions.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/content/doc/setup/versions.md b/docs/content/doc/setup/versions.md index 838fdb435..61bfd452b 100644 --- a/docs/content/doc/setup/versions.md +++ b/docs/content/doc/setup/versions.md @@ -10,7 +10,7 @@ menu: # 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 >}} @@ -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. 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. ## Switching between versions