Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: plasma-desktop@packages.debian.org, pkg-kde-talk%40alioth-lists.debian.net, hefee@debian.org
Control: affects -1 + src:plasma-desktop
Hey,
before invest time, to do the debdiff and all paperwork for Plasma 5.27.X LTS
packages, there's need to be a idea, how to get it into stable.
Currently 5.27.3 on experimental. Upstream is relasing with a fibbonacci
time frame, when stable will be release, we would be at ~5.27.5. I
wanted to ask, if we find a solution together to get the new version
into bookworm. Upstream wants to give bugfix releases over 2 years.
Plasma 5.27 is a LTS branch, that is stable and only bug fixes with be
released with next minor versions. No transitions nor API changes. By
the time the most bug fixes are around multi screen support. From my
point of view users would definitly benefit from these updates with no
negative effect.
Alternatives:
* Using backport is not an option, because upstream is switching to Plasma 6 (based
on Qt6), that will enter in sid soon after bookworm has released.
* extract all bugfixes from Plasma 5.27.X and apply them as patches on
top and remove the version bump. In the end it is a lot more work on
our plate, with no benefit for users. Upstream has much more
problems to understand, that Debian has all bugfixes included.
It is the first time we the KDE manatiner are in this lucky situation
that we can use the LTS releases from upstream. I hope we will find a
good solution together to make the user experince better and not put a
lot of work on yours/ours plate.
The NACK on #1033271 made part of the team quite unmotivated to try it
for Plasma. See the mail thread [1]
Regards,
hefee
Plasma is ~50 pacakges - see a list of packages:
https://salsa.debian.org/qt-kde-team/pkg-kde-dev-scripts/-/blob/master/tierdata/plasma.5.25.0.tier.sh
[1] https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2023-April/003467.html
Reply to: