No matter at which exact scope we end up with, since that is: - clearly a feature - very new (partially not yet merged upstream) it is hard to quick-shove this even into Hirsute :-/
Also in the past it was useful to have it in a completed upstream release to have more developers pick it up and due to that get coverage and issues reported. That can often identify required follow on fixes. Therefore on the timing of this I'd go a slightly bit slower. We might end up on this by merging the new versions early in the cycle into 21.10 and at that time re-spin the PPA builds we use here (with any later modifications that might have happened.) Until then we can already take a step at pre-verification. The PPA holds builds with the changes as identified backported to Focal (if it works). Groovy/Hirsute should be simpler than Focal once we eventually do the full set for real SRUs. Indeed TBH I'm considering to SRU these changes only to Hirsute (for being much closer to the upstream changes, more appliciable and threby less churn and regression potential). That would make it available to Ubuntu users (via 21.04 directly) and for Ubuntu LTS users indirectly via Server-Team-Backports [1] as well. I'll look at Focal and Hirsute PPAs based on this next week then. [1]: https://launchpad.net/~canonical-server/+archive/ubuntu/server- backports -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921880 Title: Add EPYC-Milan model To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
