颠覆版本‘差异’有什么大不了的？
您好，使用 VS2008 和 VisualSVN，VisualSVN 人员似乎热衷于将客户端（及其 VisualSVN 服务器）更新到最新的 Subversion 版本。
我的问题是我的颠覆服务器是一个托管服务器，似乎总是落后于我使用的客户端的几个版本。我应该担心这个版本“不匹配”吗？
关于何时需要关注（例如后面的整个主要版本）是否有一般的经验法则？
客户端、服务器或协议中是否内置了某种机制来防止“配对”不良的客户端和服务器之间发生可怕的事情？
Greetings, using VS2008 and VisualSVN and seems the VisualSVN folks are religious about updating the client (and their VisualSVN server) to the latest Subversion release.
My question is my subversion server is a hosted server and seems to always lag several versions behind the client I use. Should I be concerned about this version "mis-match"?
Is there a general rule of thumb about when it is a point to be concerned (like an entire major release behind)?
Any sort of mechanism build into either the client, the server or the protocol that prevents something horrible from happening between badly 'paired' clients and servers?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
一般来说，您不需要担心客户端/服务器版本不匹配。该协议保持一致，以防止版本不匹配的问题。除非客户端/服务器都更新，否则某些新功能可能无法使用，但这并不奇怪。
您确实需要担心针对同一工作副本使用不同的客户端，例如 TortoiseSVN 与命令行 SVN。 SVN 将在需要时自动升级工作副本，并且如果其他客户端正在使用旧版本，则它可能无法再访问。
以下是来自来源的更详细信息的链接（感谢 Dave！）
版本编号、兼容性和弃用
http://subversion.apache.org/docs/community-guide/releasing.html#release-numbering
Generally speaking you don't need to be concerned with client/server version mismatches. The protocol is maintained consistently to prevent issues with version mismatches. Some new features may not be available unless both client/server are updated, but that's not surprising.
You do need to be concerned about using different clients against the same working copy, like TortoiseSVN vs command line SVN. SVN will automatically upgrade a working copy when it needs one and if a different client is using an older version it may no longer have access.
Here's a link to more detailed information strait from the source (Thanks to Dave!)
Release numbering, compatibility, and deprecation
http://subversion.apache.org/docs/community-guide/releasing.html#release-numbering
客户端和服务器不需要完全匹配。您只需要担心与主要版本不兼容。例如从 2.xx 更改为 3.xx
The client and server do not need to match completely. You only need to worry about being incompatible for the major releases. e.g. changing from 2.x.x to 3.x.x
如果您的客户端领先于您的主机，那也没关系。客户端应该知道如何处理旧版本的 svn（过去 5 年左右我主要使用 TortoiseSVN）。当您的主机比您的客户端更新时，您可能会遇到问题，但 CollabNet 非常擅长发布更改存储库格式的版本（而且这种情况并不经常发生）。
It's ok if your client is ahead of your host. The client should know how to deal with older versions of svn (I've mainly used TortoiseSVN for the past 5 years or so). It's when your host is newer than your client that you can run into problems, but CollabNet is very good about announcing releases that change the repository format (and it doesn't happen very often).