** Description changed:

  SRU bug for Plasma 5.9.5 in Zesty
  
  We released Zesty with Plasma 5.9.4; Plasma 5.9.5 was released on April
  25 2017, so it would be nice if we could update our users to this bugfix
  point release trough -updates.
  
  Official release announcement by the KDE community:
  https://www.kde.org/announcements/plasma-5.9.5.php
  
  Complete changelog:
  https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
+ 
+ [Impact]
+ 
+  * Without this update, general users who are not inclined or able to
+ add our backports/update ppa will not receive this (possibly final)
+ bugfix release of the plasma 5.9.x release series.
+ 
+  * Providing this bugfix release via the official update pocket in the
+ archive will ensure that the bugfixes here reach and benefit most of our
+ users.
+ 
+ [Test Case]
+ 
+  * General tests:
+    - Does plasma desktop start as normal with no apparent regressions over 
5.9.4?
+    - General workflow - testers should carry out their normal tasks, using 
the plasma features they normally do, and test common subsystems such as audio, 
settings changes, compositing, desktop affects, suspend etc.
+ 
+  * Specific tests:
+    - Check the changelog: 
https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
+    - Identify items with front/user facing changes capable of specific 
testing. e.g. "Possible to edit the default color scheme" in plasma workspace, 
kwin "Fix crash on dragging titlebar buttons in System Settings."
+    - Test the 'fixed' functionality.
+  
+ [Regression Potential] 
+ 
+  * These updates fix some obvious front facing issues, but also include some 
underlying code fixes.
+   - e.g. changes for compilation under Qt versions we do not ship yet, code 
optimizations and fixes with less obvious explanation of impact in the 
changelog,
+  * Fixes for obvious and testable bugs and regressions can also introduce 
unintended other regressions in either the feature/app being fixed, or desktop 
components or subsystems that interact with it. So it is important in these 
updates to consider:
+   - General testing - does the desktop as a whole, and routine use of such 
work as previously with no obvious regressions over the previous release.
+   - If there is say a fix for the audio applet top fix one issue, in addition 
to fixing that issue, do the other common features of that app still worl as 
before, do the general audio settings still work?
+ 
+ [Other Info]
+  
+  * Packages not listed in the changelog either have a 0-diff or just 
translation updates, but have been included in the update to maintain a 
cohesive whole, and to not confuse users who expect to see all plasma 
components updated in any update release.
+ * However, we deliberately versioned depends and build depends, so that if 
accepting rebuilt small diff packages into the final release to the updates 
pocket is considered too much of a regression is or too difficult to validate, 
packages that have not introduced or require a dependency (internal or 
external) on 5.9.5 version, should be able to be abandoned from consideration 
and the SRU.

** Description changed:

  SRU bug for Plasma 5.9.5 in Zesty
  
  We released Zesty with Plasma 5.9.4; Plasma 5.9.5 was released on April
  25 2017, so it would be nice if we could update our users to this bugfix
  point release trough -updates.
  
  Official release announcement by the KDE community:
  https://www.kde.org/announcements/plasma-5.9.5.php
  
  Complete changelog:
  https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
  
  [Impact]
  
-  * Without this update, general users who are not inclined or able to
+  * Without this update, general users who are not inclined or able to
  add our backports/update ppa will not receive this (possibly final)
  bugfix release of the plasma 5.9.x release series.
  
-  * Providing this bugfix release via the official update pocket in the
+  * Providing this bugfix release via the official update pocket in the
  archive will ensure that the bugfixes here reach and benefit most of our
  users.
  
  [Test Case]
  
-  * General tests:
-    - Does plasma desktop start as normal with no apparent regressions over 
5.9.4?
-    - General workflow - testers should carry out their normal tasks, using 
the plasma features they normally do, and test common subsystems such as audio, 
settings changes, compositing, desktop affects, suspend etc.
+  * General tests:
+    - Does plasma desktop start as normal with no apparent regressions over 
5.9.4?
+    - General workflow - testers should carry out their normal tasks, using 
the plasma features they normally do, and test common subsystems such as audio, 
settings changes, compositing, desktop affects, suspend etc.
  
-  * Specific tests:
-    - Check the changelog: 
https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
-    - Identify items with front/user facing changes capable of specific 
testing. e.g. "Possible to edit the default color scheme" in plasma workspace, 
kwin "Fix crash on dragging titlebar buttons in System Settings."
-    - Test the 'fixed' functionality.
-  
- [Regression Potential] 
+  * Specific tests:
+    - Check the changelog: 
https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
+    - Identify items with front/user facing changes capable of specific 
testing. e.g. "Possible to edit the default color scheme" in plasma workspace, 
kwin "Fix crash on dragging titlebar buttons in System Settings."
+    - Test the 'fixed' functionality.
  
-  * These updates fix some obvious front facing issues, but also include some 
underlying code fixes.
-   - e.g. changes for compilation under Qt versions we do not ship yet, code 
optimizations and fixes with less obvious explanation of impact in the 
changelog,
-  * Fixes for obvious and testable bugs and regressions can also introduce 
unintended other regressions in either the feature/app being fixed, or desktop 
components or subsystems that interact with it. So it is important in these 
updates to consider:
-   - General testing - does the desktop as a whole, and routine use of such 
work as previously with no obvious regressions over the previous release.
-   - If there is say a fix for the audio applet top fix one issue, in addition 
to fixing that issue, do the other common features of that app still worl as 
before, do the general audio settings still work?
+ [Regression Potential]
+ 
+  * These updates fix some obvious front facing issues, but also include some 
underlying code fixes.
+   - e.g. changes for compilation under Qt versions we do not ship yet, code 
optimizations and fixes with less obvious explanation of impact in the 
changelog,
+ 
+  * Fixes for obvious and testable bugs and regressions can also
+ introduce unintended other regressions in either the feature/app being
+ fixed, or desktop components or subsystems that interact with it. So it
+ is important in these updates to consider:
+ 
+ * General testing - does the desktop as a whole, and routine use of such
+ work as previously with no obvious regressions over the previous
+ release.
+ 
+ * If there is say a fix for the audio applet to fix one issue, in
+ addition to fixing that issue, do the other common features of that app
+ still work as before, do the general audio settings still work?
  
  [Other Info]
-  
-  * Packages not listed in the changelog either have a 0-diff or just 
translation updates, but have been included in the update to maintain a 
cohesive whole, and to not confuse users who expect to see all plasma 
components updated in any update release.
+ 
+  * Packages not listed in the changelog either have a 0-diff or just 
translation updates, but have been included in the update to maintain a 
cohesive whole, and to not confuse users who expect to see all plasma 
components updated in any update release.
  * However, we deliberately versioned depends and build depends, so that if 
accepting rebuilt small diff packages into the final release to the updates 
pocket is considered too much of a regression is or too difficult to validate, 
packages that have not introduced or require a dependency (internal or 
external) on 5.9.5 version, should be able to be abandoned from consideration 
and the SRU.

** Description changed:

  SRU bug for Plasma 5.9.5 in Zesty
  
  We released Zesty with Plasma 5.9.4; Plasma 5.9.5 was released on April
  25 2017, so it would be nice if we could update our users to this bugfix
  point release trough -updates.
  
  Official release announcement by the KDE community:
  https://www.kde.org/announcements/plasma-5.9.5.php
  
  Complete changelog:
  https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
  
  [Impact]
  
   * Without this update, general users who are not inclined or able to
  add our backports/update ppa will not receive this (possibly final)
  bugfix release of the plasma 5.9.x release series.
  
   * Providing this bugfix release via the official update pocket in the
  archive will ensure that the bugfixes here reach and benefit most of our
  users.
  
  [Test Case]
  
   * General tests:
     - Does plasma desktop start as normal with no apparent regressions over 
5.9.4?
     - General workflow - testers should carry out their normal tasks, using 
the plasma features they normally do, and test common subsystems such as audio, 
settings changes, compositing, desktop affects, suspend etc.
  
   * Specific tests:
     - Check the changelog: 
https://www.kde.org/announcements/plasma-5.9.4-5.9.5-changelog.php
     - Identify items with front/user facing changes capable of specific 
testing. e.g. "Possible to edit the default color scheme" in plasma workspace, 
kwin "Fix crash on dragging titlebar buttons in System Settings."
     - Test the 'fixed' functionality.
  
  [Regression Potential]
  
   * These updates fix some obvious front facing issues, but also include some 
underlying code fixes.
    - e.g. changes for compilation under Qt versions we do not ship yet, code 
optimizations and fixes with less obvious explanation of impact in the 
changelog,
  
   * Fixes for obvious and testable bugs and regressions can also
  introduce unintended other regressions in either the feature/app being
  fixed, or desktop components or subsystems that interact with it. So it
  is important in these updates to consider:
  
  * General testing - does the desktop as a whole, and routine use of such
  work as previously with no obvious regressions over the previous
  release.
  
  * If there is say a fix for the audio applet to fix one issue, in
  addition to fixing that issue, do the other common features of that app
  still work as before, do the general audio settings still work?
  
  [Other Info]
  
   * Packages not listed in the changelog either have a 0-diff or just 
translation updates, but have been included in the update to maintain a 
cohesive whole, and to not confuse users who expect to see all plasma 
components updated in any update release.
- * However, we deliberately versioned depends and build depends, so that if 
accepting rebuilt small diff packages into the final release to the updates 
pocket is considered too much of a regression is or too difficult to validate, 
packages that have not introduced or require a dependency (internal or 
external) on 5.9.5 version, should be able to be abandoned from consideration 
and the SRU.
+ * However, we deliberately versioned depends and build depends, so that if 
accepting rebuilt small diff packages into the final release to the updates 
pocket is considered too much of a regression potential, or too difficult to 
validate, packages that have not introduced or require a dependency (internal 
or external) on 5.9.5 version, should be able to be abandoned from 
consideration and the SRU.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1687444

Title:
  Zesty SRU tracking bug for KDE's Plasma 5.9.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1687444/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to