[ofw] [PATCH] Bump up CI and AL interface version numbers

Fab Tillier ftillier at windows.microsoft.com
Tue Aug 26 10:22:15 PDT 2008


>  You're letting an arbitrary separation of patches dictate what the
> interface version should be.

No, I'm requesting that patches be self standing.  If a patch changes an interface such that it is no longer backward compatible, the interface version should be changed.  That applies to kernel interfaces, IOCTL interfaces, user mode interfaces, etc.

Whether the drivers supports multiple interfaces or not is irrelevant in this context.

> You don't need to bump the interface version for every single
> change - only once for a set of collective changes.  This makes
> it easier to support multiple interfaces.

Supporting multiple interfaces doesn't require supporting all interfaces that ever existed.  You could support only odd numbered interfaces if you wanted...  Just because you change an interface version number doesn't mean that interface version should be supported long term.  What's the point of a versioned interface if you're going to break backward compatibility without changing the version?

> As for release numbers, the major release numbers (should) indicate a
> change to the interface that is not backwards compatible.

Release numbers are also irrelevant in this context.

I don't understand your aversion to this - there's a benefit in changing the interface version when an interface change breaks backward compatibility, independent of release cycle.  What is the benefit in keeping the number constant?  Why shouldn't the version be changed if the interface changes break backward compatibility?

-Fab





More information about the ofw mailing list