Bug 352798

Summary: Some applications have outdated version info: but this can be automated!
Product: [Websites] bugs.kde.org Reporter: jm.ouwerkerk
Component: product/component changesAssignee: KDE sysadmins <sysadmin>
Status: RESOLVED DUPLICATE    
Severity: normal CC: christophe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description jm.ouwerkerk 2015-09-16 12:47:00 UTC
Just now I reported a bug against Kate, for which the last product version is 5.0.0 (or Git). Since I use Debian, Git is inappropriate, but the Debian (unstable) package that I use is Kate version 15.08.0.

Similarly frameworks-kio latest version appears to be 5.1 (IIRC), which again does not tally with what distributions actually ship/package these days, Debian (unstable) package version is 5.13.0.

Reproducible: Always

Steps to Reproduce:
1. Find a bug in Kate or frameworks-kio.
2. Report it.
3. Observe lack of proper up-to-date product version list on bugs.kde.org

Actual Results:  
Woefully out of date versions or versions that do not bear the slightest resemblance to what distro packages actually claim to be.

Expected Results:  
Something accurate and up-to-date, matching the distro side of things aside from distro specific version things tacked on (e.g. '-1' suffix or the '4:' prefix Debian uses for a lot of KDE apps)

But this information is already there! It's common KDE project practice to embed project version information in the cmake build files, and this information is even automatically updated by 'release scripts' (what that might be):
http://kate-editor.org/2015/07/26/kde-applications-versioning/

Please consider taking advantage of the fact that you have both the KDE projects sources (quickgit) and the release scripts, and therefore that you could automatically keep your product versions in sync by examining the relevant CMakeLists.txt after/when a new release is made.
Comment 1 Christoph Feck 2015-09-18 11:43:18 UTC

*** This bug has been marked as a duplicate of bug 335654 ***