The verification looks good and on that note I believe that it's technically ready to release, but I'm going to nitpick here and ask whether this is a valid SRU in the first place.
Per SRU policy, any bugs fixed must also be fixed in later Ubuntu releases, including any interim releases. There are two exceptions: 1. If there are two subsequent interim releases that are both current, then, as a compromise, additionally fixing only the most recent one is acceptable. 2. You cannot supply the resources to fix an interim non-LTS release, you have explicitly stated your intention to use this exception in the SRU documentation in the relevant bugs, you have marked the relevant bug tasks Won’t Fix, and an SRU team member accepts your upload on a case- by-case basis. You have not applied for exception 2; and I'm treating this as exception 1 accordingly, as I don't believe oracular contains all the fixes, and therefore the question I have is: Did you verify that all bugs fixed in 3.3.4 are also fixed in 3.5.0, or does plucky need a matching update to 3.5.1? I believe this is ok, given that you are packaging 3.3.4 and not 3.3.5 and 3.3.4 was released before 3.5.0, but really the bug should explicitly state so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109823 Title: [SRU] openvswitch 3.3.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/caracal/+bug/2109823/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
