T10755: Unifying Applications' release versions
noreply at phabricator.kde.org
Tue Apr 2 17:03:10 BST 2019
ltoscano added a comment.
In T10755#180935 <https://phabricator.kde.org/T10755#180935>, @ngraham wrote:
> In T10755#180932 <https://phabricator.kde.org/T10755#180932>, @ltoscano wrote:
> > - about the version number in the release can be probably solved - we already have some magic to create the bugzilla versions.
> Would you be interested in helping with this? We're a bit stuck in T10636 <https://phabricator.kde.org/T10636>. The idea is that we'd like the release process to automatically populate the AppData files' release tags.
Did you ask release-team@ ?
See add-bugzilla-version under sysadmin/release-tools. More details in this old thread:
About the other points, it wouldn't be the first time nor the last, where a set of components with different version numbers is distributed together, or where the advertised version or name does not match the internal number. Linux (or other kernel-based) distributions, Hadoop distributions, OpenStack releases, commercial products which aggregates various components, and so on have internal version numbers which do not match the bundle versions (and it happens also for few monolithic products like Microsoft Windows or Microsoft Office).
If we solve the issue with the population of appdata and we add the version of the bundle to the about box, would this be still an issue? As I said, I think that the name of the bundle is a more real problem from a distribution and marketing point of view than the versioning ("KDE Applications is made of KDE applications, but not all of them (?)").
To: ngraham, ltoscano
Cc: 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...
More information about the konsole-devel