T10755: Unifying Applications' release versions

Albert Astals Cid noreply at phabricator.kde.org
Tue Apr 2 22:52:59 BST 2019


aacid added a comment.


  In T10755#180974 <https://phabricator.kde.org/T10755#180974>, @hein wrote:
  
  > > Sure, why would the release team bump an individual app version if it wants to follow a random scheme?
  >
  > For the same reason the Release Team releases the app instead of an individual person?
  
  
  I personally don't agree "updating version number if you want to keep your own scheme" is a release team responsability, but you do, it's ok to disagree :)
  
  > 
  > 
  >> I think that's a really bad idea, now you have things go out of sync and people update the version in one place but not in another etc, etc etc
  > 
  > Isn't that just another subtask of "make sure everything uses version info from some central source"? I know Harald had a patch to make the website use AppStream for example.
  
  Right, we already have a central source then, it's the CMakeLists.txt file.
  
  I thought you meant "creating a repo with all the version numbers", which meant creating a similar problem to the one we have with the website.

TASK DETAIL
  https://phabricator.kde.org/T10755

To: ngraham, aacid
Cc: heikobecker, aspotashev, huftis, cullmann, 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/kde-pim/attachments/20190402/531b011e/attachment.html>


More information about the kde-pim mailing list