This has been completed a while ago in master.

Ooops, I must have overlooked that simple NOT which makes a difference: "NOT (5.42 < 5.38)" is equal to "(5.42 >= 5.38)". So it is executed and necessary. Forget what I wrote.

This is discussed in https://invent.kde.org/office/kmymoney/-/issues/37

That sounds fine. The current website requires you to click "News" then a specific release, and then there are links for the releast notes (just a list of bugs fixes) and for ChangeLog (the git log since the last release.) A more direct link to either or both of those is an improvement. I had separately emailed Thomas about trying in the future to have a more user-friendly description of the change associated with each commit or bug closure, but that's for a future discussion, I think.

@ostroffjh Agreed. The AppStream spec defines the following:

It would also be good to have quick links to the ChangeLog and Release Notes for the latest released versions. Before I add too many details, should I open a new issue on invent.kde.org or add it here?

@tbaumgart thanks then I can make some tests

Initial information about the last released source code file added to the master branch in https://invent.kde.org/office/kmymoney/commit/f0008d9c24f69adf8cf8c9a239be30b729b1ccf2

yeah we don't need more :)

@ognarb Well as I said earlier, that one is pretty straightforward : https://github.com/mcred/jekyll-xml-source/blob/master/jekyll_xml_source.rb
It downloads from an URL, convert XML to JSON and save it to a file. We don't need more, right ?

My current ruby skills are very poor but if you believe that it can be done in plain ruby it is even better :)

@ognarb then maybe we can just do it in plain ruby, that way we avoid executing commands on the system and avoid external dependencies like appstreamcli to be installed

Ok so the first thing you need to do is to update https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/org.kde.kmymoney.appdata.xml.

I added it as a subtask to https://invent.kde.org/office/kmymoney/-/issues/8 so we will have it in the upcoming release

Ok then if there is an appdata like in Krita, I can use it to get the latest versions.

I agree with @wrobelda at this point. The website should reflect the work of the development team.

@atem it could be in both, an automatic job to push the appstream xml from kmymoney repo to kmymoney-org would be easy to add. Still, better to use a single source and kmymoney own repo is best suited for this.

@wrobelda My mistake, I thought that the file would be in Kmymoney website repo but it should be in Kmymoney software repo. So the exact plugin I linked can be used as is.

@ognarb agreed, this is a better, universal solution

@wrobelda Yes _data files are one way to solve the problem. I am just worried that it's becoming a nightmare to manage.
Yes we could upstream some work done here upstream but only if it's adopted as a standard by others projects.

I think the best way would be to store the information in AppStream files and fetch the release data from there.

I am all for automation when it is documented or self-explanatory. The structure sounds like a good idea as it is extendable.

@atem You could use something like this:

@ostroffjh Ok I can do a draft in a git branch. After for the multiples releases numbers, I am waiting on @wrobelda answer.

Ah - if you mean using something like the dropdown on the vscode/visualstudio page, I do like it. Right now, it seems it's always two steps - go to the download page, then go to a separate page for the type of build, then pick your version. Saving one step for the latest version of each build type could be good.

In T12566#231526, @atem wrote:

Ok then in that case may I suggest to do like Vscode guys did : https://code.visualstudio.com/

You have a button with a dropdown that list many downloads and also other downloads that when you click go to a special page that list all downloads like we do with https://kmymoney.org/download.html

Also I am on mobile right now and I saw that the top menu does not work on mobile. But that a problem of the KDE thème because even the Konsole website has the same issue.