Re: Change to FreeBSD release scheduling etc.

On 7/15/24 15:59, Warner Losh wrote:
> On Mon, Jul 15, 2024 at 4:20 PM Colin Percival <cperciva@freebsd.org 
> <mailto:cperciva@freebsd.org>> wrote:
> 
>     On 7/15/24 15:05, Warner Losh wrote:
>      > Ideally, we'd keep the same KBI per major release, but that ideal has
>     fallen
>      > short.
> 
>     Having a stable KBI only solves half of the problem.  With DRM especially it's
>     useful for people running the latest minor release to use kmods which make use
>     of functionality which was added in the latest release before the previous
>     release is EoLed.
> 
> Functionality added where? I'm not following the point you're making here... 
> But since
> KBI stability isn't going to happen (at least given our past track record and 
> a lack of
> tools to enforce it), it may be just an academic exercise.

New functions in LinuxKPI is the case I was thinking of.  It doesn't prevent
kernel modules compiled for earlier releases working with the newer release,
but because we build kernel modules on a per-stable-branch basis we have to
wait until the previous release EoLs.

-- 
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid