debcrafters-packages team mailing list archive

[Chris Halse Rogers <2122382@xxxxxxxxxxxxxxxxxx>]

The diff looks ok, but I have some questions:

* What user-visible behaviour will change?
Two of these patches are obvious - the protocol version changes and the capability list parsing changes. What about the endpoints cache removal? What was the purpose of the endpoint cache, and what behaviours will removing it change? Could this behaviour change be perceived as a regression?

* How are we testing for regressions?
There's clearly a bluetooth conformance suite; are we running the full suite against this update, and is the conformance suite comprehensive enough to give us confidence that we won't be regressing any user? If not, how are we testing to avoid regressions?

** Changed in: bluez (Ubuntu Plucky)
       Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2122382

Title:
  [SRU] Improve audio profiles compatibility

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  In Progress
Status in bluez source package in Plucky:
  Incomplete
Status in bluez source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

   * Older Bluez not able pass the compliance testing from the Bluetooth SIG.
     This SRU aim to back port necessary patches to improve the compatibility.

  [ Test Plan ]

   * Run following test cases from Bluetooth SIG Profile Tuning Suite (PTS)
     won't get fail result.
    - A2DP/SRC/SGSIT/ATTR/BV-04-C
     - check profile version in bluez
    - AVDTP/SRC/INT/SIG/SMG/BV-07-C
     - check bluez able to issue a valid query for remote client capabilities
    - AVDTP/SRC/ACP/TRA/BTR/BI-01-C
     - check bluez can reject incorrect media transport format

  
  [ Where problems could occur ]

   * Patches are doing minor bug fix to the profile. Normal user should not be
     affected

  [ Other Info ]

   * Related upstream commits
    - https://github.com/bluez/bluez/commit/f0e9ecb9f4fe3a7bdb011dc155cf6ad657a289ee
    - https://github.com/bluez/bluez/commit/ea3f4047e452b081e34d017cce316aba9d623301
    - https://github.com/bluez/bluez/commit/f2120e3ded0656c8eda3d8058ee35654aba3fd09

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