T10755: Unifying Applications' release versions
Albert Astals Cid <[email protected]>
| Newsgroups | gmane.comp.kde.devel.games,gmane.comp.kde.devel.utils,gmane.comp.kde.devel.pim,gmane.comp.kde.devel.konsole,gmane.comp.kde.devel.kfm |
|---|---|
| Message-ID | <[email protected]> |
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