| Summary: | missing build version from AppImage | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | DrSlony <bugs> |
| Component: | Setup & Installation | Assignee: | Vincent PINON <vpinon> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | bugs, julius.kuenzel |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
DrSlony
2021-03-22 10:14:29 UTC
I don't see the need for release builds to include the commit hash. If you create bug reports with the version and packaging type (like "20.12.3a appimage") the dev team knows where to look (there are git tags for each release version on https://invent.kde.org and in fact 20.12.3a is the same than 20.12.3 concerning the source code, there is just a fix in packaging). The nightly appimage (build from master branch each day) includes a commit hash. Thanks for you report anyway :-) A tag is a description of a specific commit, so if the build I was using is made off of a tag, then yes, there is no need for a commit hash. When I opened the issue, I thought I was using a nightly build, but this was incorrect. You are right that nightly builds do include the hash. So all good. |