I think the updated justification, and regression potential sections
make a reasonable case for a hardware enablement backport.

As an aside on whether jammy should be included I can offer the
following anecdotal opinion. As the maintainer of the Ubuntu for
Raspberry Pi images, I've always followed a (strictly unofficial) policy
that we should strive to support new models of hardware in the current
interim release, with a view to backporting to the current LTS for its
next point release. For instance, when the Pi 4 came out we added
support in disco (then the devel release), then backported support to
the next point release of bionic. When the compute module 4 came out,
focal was the current release (and eoan was devel) so we simply added
support to eoan and focal, and didn't do any further backporting.

As noted this is an unofficial policy, but it's one I've attempted to
adhere to with some reasonable success, and could possibly be applied
here too (though I grant a mainframe is a very different beast, and has
a very different audience, to a pi!). By that policy, backport to noble
would be sufficient, and jammy would be out of scope.

Anyway, I'll sponsor this for plucky, and noble, and we'll see what the
SRU team say. Technically I should upload oracular too, but I suspect it
will be fully EOL before the noble backport is reviewed. Unsubscribing
ubuntu-sponsors (please re-subscribe if you also want oracular or jammy
uploading).

** Summary changed:

- [UBUNTU 22.04] GDB: Internal binutils code requires updates made for IBM z17 
in binutils already
+ [SRU] GDB: Internal binutils code requires updates made for IBM z17 in 
binutils already

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2108997

Title:
  [SRU] GDB: Internal binutils code requires updates made for IBM z17 in
  binutils already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2108997/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to