Extending the KDE Software Collection MRE
Scott Kitterman
ubuntu at kitterman.com
Wed Jul 17 19:37:22 UTC 2013
For the last 2 1/2 years there has been an MRE in place for the core KDE
Software Collection that has worked quite well. We've delivered roughly three
post-release updates per Ubuntu series since then without significant issues
(we have caught a few issues in our pre-release testing, but I don't think
there's been a problem with regressions in -updates).
Based on that success, we (Kubuntu developers) would like to extend this to
some additional packages. These are all KDE packages (developed as part of
the KDE community by primarily the same set of developers that develop the
packages that are part of the KDE SC) that follow the same guidelines for bug
fix only updates as the KDE SC (that are quite similar to the Ubuntu SRU
criteria). As part of ubuntu-sru, I have allowed some experimentation with
updates to some of these packages and they've all gone well.
Here's the added list:
amarok (no SRU history - provided via PPA, successful backport of micro-
release in lucid)
bluedevil (no SRU history - provided via PPA)
libbluedevil (no SRU history - provided via PPA)
calligra (no SRU history - provided via PPA)
kdevelop (successful SRU in quantal RC to first point release)
kdevplatform (successful SRU in quantal RC to first point release)
kscreen (successful SRU in raring, pre-1.0 bug fix update)
libkscreen (successful SRU in raring, pre-1.0 bug fix update)
lightdm-kde (successful SRU in precise for point release)
muon (successful SRU in raring for point release)
networkmanagement (no SRU history - provided via PPA)
phonon (no SRU history, releases rarely)
phonon-backend-gstreamer (one successful test in precise, additional updates
for precise/quantal pending verification)
phonon-backend-vlc (no SRU history)
rekonq (no SRU history - provided via PPA, successful backport of micro-
release in precise)
Given the testing approach we already have in place for KDE SC micro-releases,
we're confident we can safely test and deliver these additional packages to
end users post-release.
Scott K
More information about the technical-board
mailing list