** Description changed: - Backport container-stack to plucky once the update for plucky has been - completed. + [Impact] - <List exact versions being upgraded from and to for each release> - - [Impact] - TBD - - <List bug links to former cases of SRU backports for this package>[Major Changes] - TBD + In order to follow our policy on keeping the container stack (docker.io- + app, containerd-app, runc, runc-app, docker-buildx, and docker- + compose-v2) up-to-date in our supported releases, let's backport the + stack in Plucky to Oracular, Noble, Jammy, and Focal. [Test Plan] - <Link to wiki SRU backport page>TBD - [Regression Potential] - Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. - <Also, ...> + Per https://wiki.ubuntu.com/DockerUpdates, our test case is the + autopkgtests. + + [Where problems could occur] + + As usual, we deliver most benefit to our users by delivering an upstream + experience. A risk of regressions is part of that. + + [Past MREs] + + - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040461 + - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040460
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085187 Title: Backport of container-stack for plucky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2085187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
