Create track for fwupd

store-requests
1

Upstream fwupd has made it’s first ABI bump in ~8 years and due to the potential impact for regressions has forked the 1.9.x series into a 1_9_X branch.
As described in upstream fwupd/SECURITY.md at main · fwupd/fwupd (github.com) 1.9.x will continue to be supported for a while.

I would like to still be able to produce snaps both for the 1.9.x series and the 2.x.x series separately, and thus would like to open up a 1.9.x track.

1 Like
2

Any updates for this issue?

3

Hi,

Thanks for the thorough explanation. Avoiding possible regressions due to backwards incompatibility is a good case for creating a new track so I’m +1 on this.

Let’s see what others @reviewers think about this. As per the Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

Thanks,

Odysseus

4

+1 from me too - this seems like an entirely expected and normal use of tracks.

5

Hi,

2 votes in favor of creating this; the 1.9.x track has now been successfully created for fwupd.

Thanks,

Odysseus