[Bug 2109823] Re: [SRU] openvswitch 3.3.4 point release

[Julian Andres Klode]

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
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/2109823

Title:
  [SRU] openvswitch 3.3.4 point release

Status in Ubuntu Cloud Archive caracal series:
  New
Status in openvswitch package in Ubuntu:
  Invalid
Status in openvswitch source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our
  supported customers have access to these improvements.

  The update contains the following package updates:

     * openvswitch 3.3.4

  For more details see:

     * https://www.openvswitch.org/releases/NEWS-3.3.4.txt
     * https://github.com/openvswitch/ovs/compare/v3.3.0...v3.3.4

  It will include [1], [2] and [3] which can thereby be dropped from the
  delta. This removes all the patches in debian/patches folder.

  [1]: https://github.com/openvswitch/ovs/commit/e3ed764bb246e312050416f94b1e04a1569d1a5a
  [2]: https://github.com/openvswitch/ovs/commit/c560f6ca3257dd3b64e01a4a244b02b90216858b
  [3]: https://github.com/openvswitch/ovs/commit/46af8a20ca5f5301f0679b7106948b4d96b08de7

  [Test Case]

  The following SRU process was followed:

  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team will
  run their continuous integration test against the packages that are in
  -proposed. A successful run of all available tests will be required before the
  proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary of the
  executed tests. The OpenStack team members will not mark ‘verification-done’ until
  this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

  [other Info]
  ​​This is a regular update policy, it follows many others:
  - #1021530 [SRU] update to include stable fixes for OVS 1.4
  - #1470120 [SRU] openvswitch 2.3.2
  - #1641956 [SRU] openvswitch 2.6.1
  - #2003059 [SRU] openvswitch 3.0.3 point release
  - #2003060 [SRU] openvswitch 2.17.5 point release
  - #2025319 [SRU] openvswitch 3.1.2 point release
  - #2025323 [SRU] openvswitch 2.17.7 point release
  - #2039906 [SRU] openvswitch 3.2.1 point release
  - #2039907 [SRU] openvswitch 3.1.3 point release
  - #2039908 [SRU] openvswitch 2.17.8 point release

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/caracal/+bug/2109823/+subscriptions