[Bug 1949412] Re: Upgrade fwupd for Atomic Docking Support

[Yuan-Chen Cheng]

** Description changed:

  This is to support Dell's new Atomic Docking.
  
  Plan to still use 1.5.x branch given the tight schedule.
  
  It's time we start to work on upgrading to 1.7.x and splitting its EFI
  source package.
+ 
+ [Impact]
+ 
+  * Several components that are used in OEM projects need
+    to use the fwupd to support firmware update.
+ 
+  * This is be a SRU exception that follow protocol in
+    https://wiki.ubuntu.com/firmware-updates
+ 
+ [Test Plan]
+ 
+  * follow the steps in the SRU exception page.
+    Need to make sure it still works well even if secure
+    boot is on.
+ 
+  * Given fwupd 1.7.4 is so new, I think we should extended
+    the date in proposed channel like 14 days.
+ 
+  * Plan to loop existing OEM project and also request for
+    more regression tests.
+ 
+ [Where problems could occur]
+ 
+  * Think about what the upload changes in the software. Imagine the change is
+    wrong or breaks something else: how would this show up?
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
+ 
+  * This must '''never''' be "None" or "Low", or entirely an argument as to why
+    your upload is low risk.
+ 
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
+  * and address these questions in advance

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fwupd-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1949412

Title:
  Upgrade fwupd for Atomic Docking Support

Status in OEM Priority Project:
  In Progress
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  New
Status in fwupd-signed source package in Focal:
  New
Status in fwupd source package in Hirsute:
  New
Status in fwupd-signed source package in Hirsute:
  New
Status in fwupd source package in Impish:
  New
Status in fwupd-signed source package in Impish:
  New
Status in fwupd source package in Jammy:
  Fix Released
Status in fwupd-signed source package in Jammy:
  Fix Released

Bug description:
  This is to support Dell's new Atomic Docking.

  Plan to still use 1.5.x branch given the tight schedule.

  It's time we start to work on upgrading to 1.7.x and splitting its EFI
  source package.

  [Impact]

   * Several components that are used in OEM projects need
     to use the fwupd to support firmware update.

   * This is be a SRU exception that follow protocol in
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * follow the steps in the SRU exception page.
     Need to make sure it still works well even if secure
     boot is on.

   * Given fwupd 1.7.4 is so new, I think we should extended
     the date in proposed channel like 14 days.

   * Plan to loop existing OEM project and also request for
     more regression tests.

  [Where problems could occur]

   * Think about what the upload changes in the software. Imagine the change is
     wrong or breaks something else: how would this show up?

   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.

   * This must '''never''' be "None" or "Low", or entirely an argument as to why
     your upload is low risk.

   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1949412/+subscriptions