https://bugs.kde.org/show_bug.cgi?id=399730
--- Comment #2 from ocumo <kxk-ocumoatbugs...@lugosys.com> --- (In reply to emohr from comment #1) Thank you for your contribution. Unfortunately, this happens regardless of how up-to-date this system is (updated daily, sometimes twice a day). The good thing about Linux is that it doesn't suffer from the kind of issues one see in certain commercial Operating System since 30 years, in which the switching off and then on again ritual seem to somehow "cure" the oddest bugs. The bad thing about Linux is that there are so many ways to package your source code, that developers end up having a huge ecosystem of distros to package for, and then they fail to properly follow up on all of them. On top of that, some projects also fail to have their main webpages updated. The Kdenlive package that I have installed, is the current version in the Ubuntu repositories. Guess what, it's very dated: v18.04.01, compared to what I see is the latest release (18.08.2). To make things muddier than mud, the Kdenlive download page, in the "Ubuntu" section, says (quote as of the time of this post in https://kdenlive.org/en/download/, 2018-10-19T20:14:18.867Z): "It is recommended to download the AppImage version until the release of Ubuntu 18.04.". Well, two possible comments to that: 1) "Just use the Appimage, why complain?" Or...2) "Ubuntu 18.04 has been released 6 months ago, so I am good to use the normal repo." Now: who is right? We could be arguing for long time, but let's agree on this: If the documentation is confusing/outdated/obsolete... how can users know what is right without double checking every page against other pages, news, blogs, forums or whatever? Turns out there is some "News" page (which other projects call different names or simply don't have) mentions the new releases. I don't care for "news" pages except real world ones. But again: I have hundreds of applications that I need to update, besides the system's. Users seem to be expected to read all the "News" of all their applications, in pure Windows 95, 198x style. But then, since one couldn't trust the documentation anyway, one would be forced to double check through hundreds of webpages. Or... spend spend time writing bugs reports about obsolete things nobody should be using or caring. I am truly sympathetic with the F.O.S.S. developers, I do. But _precisely_ because of that, I know that the best projects are very difficult because they do handle the difficult part (the wild ecosystem) well. Not because they have a lot of resources. But because the do communicate the essential efficiently. If a project doesn't do the basic stuff reasonably, then we get a ridiculous situation like this: A fool writing a bug report on an obsolete package, wasting his and others time, plus polluting the kde bugs system. That's a shame, dear devs. Either update your documentation or don't document at all. You can only maintain or increase your users base if you help them do the basic: install, upgrade in time, not too late. Anything else is irrelevant if this is not done properly, you know? There is no point in offering code without helping people to avoid using obsolete one. Is there anyone around still convinced that basic installation/upgrading documentation is a luxury in the F.O.S.S. world? I am not going to start reading the Kdenlive news every morning together with my real world News sources. And I have not even tried the appimage version, nor I am very excited to try it right now, regardless of the bug existing or not. -- You are receiving this mail because: You are watching all bug changes.
