In my opinion, this SRU is unacceptable as-is. The stated impact is:
> Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application OK. That's a pretty common HWE issue, and something that can be addressed in SRU. Let's look at the test plan: > Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications OK. Maybe a bit sparse. But, not uncommon for these kinds of HWE SRUs either. What about regression potential? > This SRU going to improve UCM handling and may affect the audio behavior. This is where I start to have issues. These are *massive* changes you are proposing in noble. Yet, the test plan contains nothing more than the *very* specific HWE use case. There is no attempt whatsoever to cover the stated regression potential in the test plan. And, given the massive patch set, the regression potential appears significant. Given all of that, the impact of this bug simply does not seem to warrant the risk involved here. To summarize, while I agree that this sort of bug is acceptable for SRU in principle, the current proposal is unacceptable because: - the changes are far from minimal - the risk significantly outsizes the impact of the bug - the test plan does not attempt to address that risk whatsoever I am rejecting the noble upload on that basis. From a glance, the plucky upload seems more reasonable, but I am not reviewing it at this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122556 Title: 3.5mm microphone recognized but can’t be used as audio input To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2122556/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
