touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

** Changed in: autopilot (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: autopilot-qt (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: mir (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: window-mocker (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: xpathselect (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1282593

Title:
  [FFe] standing freeze exception in trusty for autopilot components and
  Mir packages

Status in “autopilot” package in Ubuntu:
  Fix Released
Status in “autopilot-qt” package in Ubuntu:
  Fix Released
Status in “mir” package in Ubuntu:
  Fix Released
Status in “window-mocker” package in Ubuntu:
  Fix Released
Status in “xpathselect” package in Ubuntu:
  Fix Released

Bug description:
  Dear release team,

  I would like to request a blanket FFe for the autopilot and mir
  components listed below. I separated this request from
  https://bugs.launchpad.net/ubuntu/+bug/1282590 as those are particular
  cases in my opinion.

  Indeed, autopilot components are used to validate the state of some
  components on the desktop (like unity7) before releasing. However,
  they are not included in any flavor image and so not part of the final
  product. I think as Touch needs will probably evolve, there are high
  chances that changes will be needed in them, and so prefer to cover
  them.

  Autopilot stack
  autopilot
  autopilot-qt
  window-mocker
  xpathselect

  Mir stack: (note that unity-mir, unity8, unity-system-compositor and platform-api are touch only and so, covered by the other FFe)
  mir

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