Rebase policy for linux-firmware

[Josh Boyer]

On Wed, Sep 11, 2013 at 01:03:09PM +0000, "Jóhann B. Guðmundsson" wrote:
> Hi
> 
> Looking into koji for linux firmware I see
> 
> linux-firmware-20130724-30.git31f6b30.fc20
> linux-firmware-20130724-29.git31f6b30.fc19
> linux-firmware-20130724-0.3.git31f6b30.fc18
> 
> and my question are these
> 
> Do we have a firm rebase policy for linux-firmware?

The current method is to grab whatever is the latest upstream every few
weeks and put it into rawhide.  For stable releases, we tend to update
it if new hardware support lands (e.g. new iwlwifi firmware), or if
we're going to do a kernel rebase that has drivers requiring new
firmware (e.g. the radeon drivers in 3.10/3.11).

That isn't documented anywhere, so "firm" and "policy" would be hard to
apply but it's what I've been doing for a while now.

> as well as
> 
> can we adapt the release numeric scheme we use in the kernel?
> ( as in something like... )
> 
> linux-firmware-20130724-300.fc20
> linux-firmware-20130724-200.fc19
> linux-firmware-20130724-100.fc18

Possibly.  Is there some problem you're looking to solve with this?

The firmware packages are noarch and don't have config settings, so
there's really no reason linux-firmware-20130724-X couldn't be used on
any given Fedora release.  The kernel package within that release will
enforce which version of linux-firmware is required.

josh