[ofw] [PATCH] Bump up CI and AL interface version numbers
Hefty, Sean
sean.hefty at intel.com
Mon Aug 25 16:56:30 PDT 2008
>Wrong - the versions should change any time the interface changes (not if
>there's new functionality added, but if there's a change to an existing
>interface.) If you build something from the tree and try to update an existing
>install you can end up with systems in a perpetual crash/reboot cycle if the
>interface changed but the version didn't. Move pointers around (like swapping
>the p_next and wr_id in the ib_send_wr_t structure) and you'll get a crash if
>both the client and provider of the interface don't agree on what the interface
>looks like.
You set the version number at the end of the development cycle, immediately before the release, rather than continually bumping it up with every check-in. Our next release is 2.0, not 13.0 or 1505 - the WinOF version is only changing once for this release. The same principles apply whether you're talking about a software package, a single library, or a driver.
The problem you had is that you tried to pull part of a development tree and have it work with a different part of the tree. An SVN check-in is not a release, and doesn't have a version number associated with it.
- Sean
More information about the ofw
mailing list