Skip to content

Conversation

@superm1
Copy link

@superm1 superm1 commented Dec 5, 2025

Description

Update the fwupd exception documentation to match the reality today

  • Drop the handling for old releases that confused things
  • Make it explicit that major versions aren't covered

Related issue

https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2131001

Checklist

* Drop the handling for old releases that confused things
* Make it explicit that major versions aren't covered
Metadata
--------

Due to this, upstream highly recommends distros to not backport
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAK. Upstream recommendations do not form SRU policy, and in this case contradicts SRU policy. Please do not emphasize this more. If anything, this should be removed because it implies that minimal patches to fix specific bugs are to be discouraged, contrary to Ubuntu SRU policy.

New versions of fwupd and fwupd-efi can both be SRU'ed into older
releases provided following process is followed:

**fwupdate**: tarball releases only. No backported individual patches.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No backported individual patches.

That may be your preference, but it's not the position of the Ubuntu SRU team. Please remove this. I appreciate it was there before; I don't know how that slipped in.

**fwupd-efi**: tarball releases only. No backported individual patches.
If a tarball release isn't available, make upstream release one.

**fwupd**: fwupd releases in the 1.0.x series.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make it explicit that these are upstream microreleases only.


Updating to a new major series is not an unsurmountable ask for extreme
circumstances, but this policy does not explicitly allow it and it needs
to be treated more scrutiny.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"not explicitly allow it"? No thank you, since this implies that it might be being permitted by implication. If anything, this should say "this policy addresses microreleases only".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants