T10755: Unifying Applications' release versions

Eike Hein noreply at phabricator.kde.org
Tue Apr 2 16:45:52 BST 2019

hein added a comment.

  My gut reaction was to agree with @ltoscano whole-heartedly, but the more I think about it that stance does have awkward unsolved problems.
  The red flag is "Going out may make the original version useless and have more impact on packagers (epoch)" - we shouldn't make things worse for users for the sake of packager convenience, that defeats the point of releasing software for use.
  The Apps version number is what we announce, promote, etc. It's what users mentally deal with. It's what they read about, look forward to, want to update to, find references to online, etc. The argument that it is what should show up in package managers and About dialogs is quite strong. So initially I thought "We just need to slap Released-with-apps-<foo> as a second line into the About dialog", but that won't fix what you see in package managers.
  the pain
  That said, Luigi is right that an app exiting the bundle is forever locked into continuing with a YY.MM version numbering scheme then so their semver keeps increasing. That's pretty meh, but users may not care.


To: ngraham, hein
Cc: hein, ltoscano, kde-utils-devel, #kde_games, #kde_pim, sitter, jriddell, #spectacle, #gwenview, #konsole, #kate, #dolphin, aacid, cfeck, #kde_applications, ngraham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/konsole-devel/attachments/20190402/f3bb7992/attachment.html>

More information about the konsole-devel mailing list