Since x265 was NAKd, is this and related MIRs still valid?
libheif depends aom [0] which is incomplete. MIR and Security have conditionally ACK'd, and owning team needs to satisfy conditions.
aom depends on libyuv [1] which is incomplete. MIR team conditionally ACK'd. When conditions are satisfied by owning team, the MIR will be assigned to Security.
aom depends on libwebm [2] which Ubuntu Security will ACK soon.
libheif depends on dav1d [3] which is incomplete and not yet ready for MIR team review.
libheif depends on libde265 [4] which needs an Ubuntu Security review.
libheif depends on x265 [5] which was NACKd by Ubuntu Security.
Since x265 was NAKd, is this and related MIRs still valid?
libheif depends aom [0] which is incomplete. MIR and Security have conditionally ACK'd, and owning team needs to satisfy conditions.
aom depends on libyuv [1] which is incomplete. MIR team conditionally ACK'd. When conditions are satisfied by owning team, the MIR will be assigned to Security.
aom depends on libwebm [2] which Ubuntu Security will ACK soon.
libheif depends on dav1d [3] which is incomplete and not yet ready for MIR team review.
libheif depends on libde265 [4] which needs an Ubuntu Security review.
libheif depends on x265 [5] which was NACKd by Ubuntu Security.
[0] https:/ /bugs.launchpad .net/ubuntu/ +source/ aom/+bug/ 2004442 /bugs.launchpad .net/ubuntu/ +source/ libyuv/ +bug/2004516 /bugs.launchpad .net/ubuntu/ +source/ libwebm/ +bug/2004523 /bugs.launchpad .net/ubuntu/ +source/ dav1d/+ bug/2004446 /bugs.launchpad .net/ubuntu/ +source/ libde265/ +bug/2004449 /bugs.launchpad .net/ubuntu/ +source/ x265/+bug/ 2004453
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/