vikunja/website
2
0
Fork 4
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: clarify unstable version
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
kolaente 2024-12-12 12:22:48 +01:00
parent feabd92f90
commit 443953574a
Signed by: konrad
GPG Key ID: F40E70337AB24C9B
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/content/docs/setup/versions.mdoc
View File

@ -25,6 +25,11 @@ 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.20.2-75-6049427322`
It might happen that the unstable version does not seem to be based on the latest release.
For example, the version might report `v0.24.1-566-gb3040b846` when the last release is `v0.25.5`.
This does not mean the unstable builds are outdated. Depending on the release, we only backport changes to patch releases.
The important part is the commit hash at the end, which you can verify [in the git repo](https://code.vikunja.io/vikunja).
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.