对于非技术客户来说非常简单的版本控制
我们开发了一个系统，客户可以使用工具创建自己的内容并保存为 XML。可以预见的是，他们将版本存储在无数的文件夹中并重命名文件等。并且可以预见的是，他们已经至少丢失过一次工作。
我们不对他们创建的内容负责，但如果能帮助他们解决问题就太好了。是否有任何真正简单的系统我们可以推荐给他们...我们不希望他们使用我们的 VCS，即使他们能弄清楚，因为我们随后会收到支持请求。
更新 我们甚至不需要客户端-服务器设置。这是为了阻止他们意外地保存他们的主版本，而不是提供备份......我们保留官方版本的备份，但他们在迭代过程中在本地处理它们，并为我们提供最新版本以包含在版本中。
We've developed a system which involves the customer using a tool to create their own content, saved as XML. Predictably they are storing versions in a myriad of folders and renaming files, etc. And predictably they've already lost work at least once.
We're not responsible for the content they create but it would be nice to help them out. Are there any really easy systems we could recommend them... we don't want them using our VCS even if they could figure it out, as we'd then be getting support requests.
update
We don't even need a client-server setup. It's about stopping them saving over their master version by accident, rather than providing a backup... we hold backups of the official versions but they work on them locally during an iteration and give us the newest version to include in releases.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
Subversion 有一个称为自动版本控制的功能，其中通过 WebDAV（又名 Microsoft Web 文件夹）安装的目录将在保存到该目录时自动创建新版本。对于最终用户来说，只需一个特殊的文件夹来保存内容。
Subversion has a feature called autoversioning where a directory mounted via WebDAV (aka Microsoft Web Folders) will automatically create a new version upon a save to that directory. To the end user, there's simply a special folder to save things in.
据我所知，没有任何版本控制系统对于“没有经验的”用户来说是“容易”使用的 ->还请记住，您必须维护一个服务器-客户端环境来操作这样的系统...或者采用托管方式，但同样，没有可用的“简单”系统...
也许会考虑一些替代方法，例如 dropbox。 com 可能是一个替代方案。他们还跟踪版本。
to my knowledge there are no version control systems which are "easy" to use for "unexperienced" users -> keep also in mind that you have to maintain a server - client environment to operate such a system... or go the hosted way, but there again, no "easy" systems available...
maybe looking at some alternative methods like dropbox.com could be an alternative. they also keep track of versions.
您可以将 TortoiseSVN 与 Subversion 服务器结合使用。只要他们理解更新和提交，就应该没问题。
You can use TortoiseSVN with a subversion server. So long as they understand update and commit, they should be OK.
将主存储替换为数据库，使用具有某种方法来指示文件版本的表，然后添加“导出到 XML”或“保存到 XML”功能，然后创建所需的输出。比尝试使用完整的 VCS 更干净，这无疑会造成不必要的混乱。
Replace the primary store with a database, using a table that has some method for indicating the version of the file then add an 'Export to XML' or 'Save to XML' function that then creates the output they need. Cleaner than trying to involve a full VCS which will undoubtedly cause more confusion than is necessary.
我喜欢上面的答案，但他们总是可以使用 Sharepoint（wss - 免费版本）中的文档库功能。只要他们使用的站点位于端口 80 上，它就可以使用 WebDAV。这是存储 xml 的一步，而且它是共享点，因此业务用户很容易破译。版本控制几乎会在每次保存时保存一个新版本，对于 Office 文档，无需太多考虑即可使用，而对于其他文档，他们需要上传它。
I like the above answers but they could always use the document library feature in Sharepoint (wss - free version). it can use WebDAV as long as the site they are using is on port 80. This is one step up from storing xml, and it is sharepoint so it is pretty easy for business users to decipher. The versioning will pretty much save a new version on each save, for Office documents this works without much thought and for other documents they will need to upload it.