Zum Inhalt

Release Matrix and Versioning

weekly monthly beta be lts customer customer be/lts nightly
releases next next beta be lts customer customer branch every branch is possible
releases eg. main main 2026.11 2025.11 2024.11 metaways/main customer/2025.11 pu/fix/packaging
git tag weekly-<year>.<weeknumber>.<counter>[*] main-<date>.<counter>[*] <tine version>-<data>.<counter>[*] <tine version>.<counter>[*] <tine version>.<counter>[*] <tine version>.<counter>-<customer><counter>[*] not tag =, but version is nightly-<branch with / replaced by - >-<year>.<month>.<day>-<short commit sha>
tag eg weekly-2025.31.1 main-2026.02.15.2 2026.11-2026.08.07.1 2025.11.4 2024.11.4 metaways-main-2026.01.29.1(pl10) 2025.11.7-customer1 nightly-pu-fix-packaging-2025.03.28-g19ebe82e
triggered by schedule - weekly by tag (conventionally every 3. Thursday of a month) by tag (conventionally every 3. Thursday of a month) by tag (conventionally every 3. Thursday of a month) by tag (conventionally every 3. Thursday of a month) by tag / by schedule (depends on the customer) by tag schedule / merge request
github release as pre release no as pre release as latest no no no
dockerhub tag weekly, git tag no tine version without .11, git tag latest, tine version without .11, git tag tine version without .11, git tag no no
vpackages no no no tine20.com/maintance, set current link tine20.com/maintance customer repo, set current link, optional for debug purposes
gitlab packages weekly monthly beta tine20.com no customer name / configurable no
customer registry tag no no no no no git tag, -, latest no
version check no no no yes no no no
tine edition be (but with beta license) be be be be be -