T10812: KDE Applications

Nathaniel Graham noreply at phabricator.kde.org
Thu Apr 18 21:45:12 BST 2019

ngraham added a comment.

  In T10812#182195 <https://phabricator.kde.org/T10812#182195>, @aacid wrote:
  > > Apps that are in the bundle have inconsistent versioning; most use the bundle's own versioning scheme, but others use their own
  > I personally disagree this is a problem. It let's applications hop on and off the release and keep their versioning number intact.
  I'm using Dolphin 18.12.3, which comes from KDE Applications 18.12.3. But the bundle it also comes with Okular. Am I using Okular 18.12.3? Or Okular 1.6.3? The promo material says 18.12.3. The version number in my distro's packaging says 18.12.3. Discover, which uses the distro packaging metadata, says 18.12.3. But the About Okular window says 1.6.3. This is confusing and problematic from a user, packager, and promo perspective because it's not clear which version number they should use.
  In T10812#182195 <https://phabricator.kde.org/T10812#182195>, @aacid wrote:
  > > The bundle's YY.MM version numbering scheme happens to be the same as Ubuntu's versioning scheme, which causes users to confuse one with another (for example a user with Kubuntu 18.04 is actually using KDE Applications 17.12, not 18.04)
  > I personally disagree this is a problem. Ubuntu didn't invent the YY.MM versioning scheme, on top of that our scheme only overlaps with Ubuntu's 1/3 of the times. Maybe Kubuntu can just put some extra work and make sure that for the .04 release they ship our .04 release if they feel that it confuses their users. Or maybe they could change their versioning scheme.
  If you're suggesting that Kubuntu could change their versioning scheme, that's a tacit admission that you do think there's a problem (otherwise there would be no suggestion of a proposed change or solution). It's a problem from a user perspective for just the reason I gave: users confuse our app versions with Ubuntu's own version numbers. "Confused users" is a problem. I agree that it's not a huge issue but I think it //is// an issue. Maybe it's not worth fixing. But it's an issue.
  In T10812#182195 <https://phabricator.kde.org/T10812#182195>, @aacid wrote:
  > > There are no LTS app versions the way there are with Plasma; distros that ship Plasma LTS get stuck with old apps versions that have bugs which have been fixed in later releases
  > I personally disagree this is a problem. If distributions want bug fixes they can either
  > - update to a new release
  > - do the work of doing an LTS branch themselves.
  > - give us money so we can hire someone to the work for them
  Updating to a new release isn't an option for the discrete release distros, particular for their LTS releases. Asking them to do an LTS branch themselves or pay us to do it is unreasonable; it's our software and we define our release schedule. All I'm saying is that I think adding LTS versions of apps is something that would be really nice for the discrete release distros that ship our LTS Plasma versions. Right now they can continuously take our LTS Plasma bugfix releases to ensure that the Plasma they ship gets better and better over time, but they can't do this for our apps. This isn't just bad for their users; it's bad for us because we need to handle more time-wasting bugzilla tickets for issues that have already been fixed from people using versions of our software that could be 2 or more years old.
  > If this comes from an application developer that wants to maintain 3 branches (LTS, stable, devel) it'd be another thing. Do we know of any developer that would like to maintain such scheme for KDE Applications?
  I mean, that's what we do for Plasma and it's not a problem. In practice all it means is that when you have a bugfix, instead of landing it on the stable branch and merging to master, you land on the LTS branch, merge to the stable branch, and merge that to master. And in the few cases where it doesn't apply cleanly to the LTS branch, you say, "ehh, too much work, stable or master only" and life goes on. :) It's really not that hard.


To: ngraham
Cc: aacid, #yakuake, #okular, #dolphin, #kate, #spectacle, #konsole, #gwenview, #kde_pim, #kde_games, #kde_applications, ngraham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/konsole-devel/attachments/20190418/332b337b/attachment-0001.html>

More information about the konsole-devel mailing list