| Summary: | Use different version scheme for beta tags | ||
|---|---|---|---|
| Product: | [Applications] kasts | Reporter: | Salvo "LtWorf" Tomaselli <tiposchi> |
| Component: | general | Assignee: | bart |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | minor | CC: | nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 23.08.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Salvo "LtWorf" Tomaselli
2023-12-12 16:08:05 UTC
Sorry to close this bug report right away, but there is literally nothing I can do: this is the versioning scheme for the entirety of KDE (gear) which includes more than a hundred packages. The whole release procedure is fully automated, and I wouldn't even know how to do a release manually. :-) So if you would like to request a change, please do so against KDE gear itself. PS: I do agree up to a certain point that the current versioning scheme can cause unwanted problems, because I had similar issues with a beta release with a higher number blocking the automated flathub package update of the stable version. You can use https://release-monitoring.org/project/326638/ to monitor releases. It also knows how to distingiush between regular and prereleases That link illustrates the problem: Latest version 24.01.80 which is NOT the latest version :D I will ask to the other kde maintainers how they deal with this issue. I see now that I am supposed to look at the detailed long list of things, not the main summary. Thing is that here: https://tracker.debian.org/pkg/kasts it permanently looks like it's on an old version. |