Thanks for the ping Vlad, The old FAQ declaring it not ready yet these days is
(quote):
"Is PipeWire ready yet?
It is getting ready for broader testing.
The API in master is now declared stable and not expected to change anymore for
the
0.3 release.
The protocol can support older 0.2 version clients transparently. This means
that flatpaks
with older PipeWire libraries can connect to a newer daemon."
=>
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#is-pipewire-ready-yet
We will need to ping the Desktop Team if this still would be their path
of choice and if they want it to re-enter security evaluation.
Assigning to seb128 who did the last Desktop-direction statements on
this in comment #1.
@seb128 - would you mind discussing this with the Desktop Team?
- if you think this is important these days and you want it to re-enter
security assign it
to ubuntu-security please
- if changes in the infrastructure happened and this is no more needed/wanted
could
you explain here why and then set it to a "Won't Fix" which would be more
clear in
regard to peoples expectations.
** Changed in: pipewire (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
