> I think that means, in retrospect, we should have released 1.6 then, right > before merging demand-attach. Then at least all that code cleanup and > related work would have gotten into stable, and while the release wouldn't > have been particularly exciting, it would mean that people developing > against it would only have had to deal with the demand-attach differences, > not lots of niggling little differences from code cleanup.
Well spoken. The question is now how to move forward. So how would you folks who have worked with 1.5.X describe the status of the current * 1.5.X server * 1.5.X *nix client ? Harald. _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
