[OpenAFS] OpenAFS and windows/unix versioning

chas williams - CONTRACTOR chas@cmf.nrl.navy.mil
Wed, 7 May 2014 09:34:14 -0400

On Tue, 6 May 2014 17:04:25 -0500
Andrew Deason <adeason@sinenomine.net> wrote:

> The reason we don't do this now, and the argument for why we should
> continue to not do this, is that Windows releases tend to happen much
> more frequently than Unix releases (look at 1.6.x vs 1.7.x, though it
> shouldn't always be quite that bad). The reasons for this I believe are
> that the Windows client sometimes needs to make drastic changes quickly
> due to changes imposed by Microsoft in Windows itself or other
> components. This can happen on other platforms, too, but what I've been
> told is that this a much bigger issue on Windows than anywhere else. In
> extreme cases this may affect non-Windows parts of the code, and so the
> stability of Unix releases could be affected even though Unix releases
> gain none of the benefits.

Since the Windows release is really just the client (AFAIK) I don't see
any reason to keep it in lock step with the Unix releases.

This leads to the next logical step that perhaps the servers and
clients could be released separately on Unix as well.  If you screw up
a server release you affect potentially thousands of people.  If you
screw up a client release, you only affect those that installed it and
the fix is easy enough.

This would let the Unix client versions move ahead a little faster.

Personally, versions are just numbers.