version status page
Open, Needs TriagePublic

Description

create overview page which lists which version of things we have. things being release bundles (frameworks/plasma) or invidual extragear apps. IT DOES NOT MEAN PACKAGES.

to that end we probably need tech to map a package to their upstream identity

sitter created this task.Aug 14 2018, 11:00 PM
jriddell renamed this task from version statuts page to version status page.Oct 3 2018, 9:45 AM

You know, I feel like appstream can help us here. Certainly with the individual extragear apps. We could simply crawl all application appstream components we have packaged, then exclude all which aren't clearly KDE, then exclude all which are from a package that is in a release bundle and presto we have nice metadata to render into a website.

On a related note: determining release bundle versions is probably as simple as interrogating projects.kde.org api -> pick repo in bundle -> check if we have a neon packaging repo of the same name -> get version from there. And this in turn may overlap with what's needed for T10285 to a degree. Both tasks ought to be somewhat the same, except the task at hand only needs one repo and T10285 does additional processing with the extracted metadata. So, all things considered we could build data extraction logic for T10285 and use the exact same code for the task at hand.

I do wonder if we even should care about extragear. That may just complicate things?

Apps / Frameworks / Plasma seems the main use case, although individual extragear apps would also be interesting

https://build.neon.kde.org/view/mgmt/job/mgmt_version_list_bionic_user/

we have the data now but I'm unsure how to proceed

[18:22] <sitter> JonathanRiddell-: I'm not quite sure what to do with the html we could pop it into the metadata domain and iframe it on the website, but then I am also not sure where to put it on the website https://build.neon.kde.org/view/mgmt/job/mgmt_version_list_bionic_user/2/artifact/versions.html
[18:22] <sitter> also the squishing problem I mentioned earlier screws this plan, so that needs fixing IMO

(squishing is about the page content being super squished against the navbar on all pages which looks like crap because the table basically sits right underneath the navbar text for that specific page)