Kubuntu Updates policy
For any update, Qt and KDE versions must match. Major Qt versions will not be put in -proposed, -updates, or -backports. Qt is used by too many non-KDE packages and part of the platform that needs to be stable. Micro-version updates of Qt would have to be considered on a case by case basis by Kubuntu developers and the Ubuntu SRU team and are unlikely to be accepted.
-updates is promised to be regression free. First, KDE microversion updates will be uploaded to a PPA and tested. Additionally, upstream bug reports and svn commits will be monitored for signs of regression. If regressions are detected, they will be resolved before moving forward. Once PPA testing is satisfactory, the packages will move to -proposed and the testing process will continue with a broader audience. Once testing is complete and the packages are sufficiently aged, they will be copied to -updates. As a matter of practice, KDE upstream limits changes for post-release updates to bug fixes and so KDE micro-version updates will likely be suitable for Ubuntu post-release updates, but in cases where they are not, it may be necessary to decline an update or remove problematic changes. There is a draft policy for this, but it has not been formally approved.
If regressions are detected, they will be worked with upstream and resolved (as long as we have alignment between the Qt/KDE versions that upstream expects, they support this policy). If for some reason an update has a regression that cannot be resolved, if it's minor, the update can be provided via backports (a decision to be made in conjunction with ubuntu-backporters) or if to severe only through a PPA or not at all.
When a new version is uploaded to -proposed, one bug with tasks for all affected packages should be opened and each package should close it in its changelog. This bug will be used to track (via comments) verification of each package. Once all packages are verified, then the bug can be tagged verification-done.
If approved by the Ubuntu Technical Board, this policy would be implemented starting with KDE 4.4.X in Lucid (already tested and ready for -proposed).
Review
This proposal was reviewed by the Kubuntu development community and received positive feedback: https://lists.ubuntu.com/archives/ku...er/003272.html
This policy was approved by the Ubuntu Technical board on November 16, 2010 and should not be edited.
For any update, Qt and KDE versions must match. Major Qt versions will not be put in -proposed, -updates, or -backports. Qt is used by too many non-KDE packages and part of the platform that needs to be stable. Micro-version updates of Qt would have to be considered on a case by case basis by Kubuntu developers and the Ubuntu SRU team and are unlikely to be accepted.
-updates is promised to be regression free. First, KDE microversion updates will be uploaded to a PPA and tested. Additionally, upstream bug reports and svn commits will be monitored for signs of regression. If regressions are detected, they will be resolved before moving forward. Once PPA testing is satisfactory, the packages will move to -proposed and the testing process will continue with a broader audience. Once testing is complete and the packages are sufficiently aged, they will be copied to -updates. As a matter of practice, KDE upstream limits changes for post-release updates to bug fixes and so KDE micro-version updates will likely be suitable for Ubuntu post-release updates, but in cases where they are not, it may be necessary to decline an update or remove problematic changes. There is a draft policy for this, but it has not been formally approved.
If regressions are detected, they will be worked with upstream and resolved (as long as we have alignment between the Qt/KDE versions that upstream expects, they support this policy). If for some reason an update has a regression that cannot be resolved, if it's minor, the update can be provided via backports (a decision to be made in conjunction with ubuntu-backporters) or if to severe only through a PPA or not at all.
When a new version is uploaded to -proposed, one bug with tasks for all affected packages should be opened and each package should close it in its changelog. This bug will be used to track (via comments) verification of each package. Once all packages are verified, then the bug can be tagged verification-done.
If approved by the Ubuntu Technical Board, this policy would be implemented starting with KDE 4.4.X in Lucid (already tested and ready for -proposed).
Review
This proposal was reviewed by the Kubuntu development community and received positive feedback: https://lists.ubuntu.com/archives/ku...er/003272.html
This policy was approved by the Ubuntu Technical board on November 16, 2010 and should not be edited.
I especially like the link between Qt version and KDE version, which means that the Qt which the KDE dev crew is using to build the installed version of KDE will be the same version of Qt installed when Kubuntu is installed. Or, if KDE4 is updated, the Qt will update to match the version of Qt used to build KDE4.
It makes it so much easier for folks, as well as being an extra feather in our cap 
Comment