2 commits

Author	SHA1	Message	Date
Felix Boucher	898444dd3c	versioning: add build version as windows build argument ... The application currently has a different build version than the one set in Jenkins. This causes issues in the crash reports on windows where they contain a different build version than the one defined on Jenkins. This leads to the names of the build artifacts on dl.jami.net not matching the crash report's build version. Changes: - Add build version as parameter to the build-windows.py script. - Propagate build version value to the application through the BUILD_VERSION symbol. - Deprecate version.h file and VERSION_STRING symbol. GitLab: #2045 Change-Id: I7986679aaeebf2bcbbd63a781499f5a50e089712	2025-06-12 13:31:59 -04:00
Andreas Traczyk	b7fb63ae40	versioning: use app/jamicore git SHAs as the version ... Currently, the user-facing version number in the about dialog, is a build-time timestamp that does help us isolate the project versions accurately. Ultimately, we need to be able to reproduce issues present in specific versions of Jami. This commit introduces a new version number in the form: <client_sha>.<jamicore_sha>, allowing us to reproduce builds more accurately. Gitlab: #1820 Change-Id: Ie7e20b20da65284e33e745996c410f539b65080c	2024-10-08 16:19:20 -04:00