Problem
The application UI currently displays a version number, however the repository continues to receive commits after a release.
As a result, a user building OpenMES from the latest source may see the same version number as the official release even though additional changes are present.
Example:
- Official release: v0.19.0
- Current source: v0.19.0 + several commits
Both builds may display:
This makes support, troubleshooting, and bug reporting more difficult because the exact source revision cannot be identified from the UI.
Expected behavior
The About/System Information page should display:
- Release version
- Git commit hash
- Optionally build date
Example:
Version: 0.19.0
Commit: bb81958
Build Date: 2026-08-17
or
Version: v0.19.0-15-gbb81958
Benefits
- Easier debugging
- Accurate bug reports
- Clear distinction between release builds and development builds
- Standard open-source practice used by many projects
Problem
The application UI currently displays a version number, however the repository continues to receive commits after a release.
As a result, a user building OpenMES from the latest source may see the same version number as the official release even though additional changes are present.
Example:
Both builds may display:
This makes support, troubleshooting, and bug reporting more difficult because the exact source revision cannot be identified from the UI.
Expected behavior
The About/System Information page should display:
Example:
or
Benefits