单独开发者的最佳版本控制 [英] Best Version control for lone developer

问题描述

我现在是一个独立的开发者，请分享您关于单独开发人员的良好VC设置的经验。

我的约束是;
$ b

• 我在多台机器上工作，需要保持同步


• 有时我离线工作

我正在使用Subversion（只是客户端到远程服务器），而且工作正常。我对Mercurial和git DVCS感兴趣，但没有一个用例对我的情况有意义。

编辑：我将我的主动开发迁移到化石<在与客户端进行试用之后，可以使用http://www.fossil-scm.org/?hl=zh-CN。我非常喜欢自动同步我的存储库（减少意外分叉）的功能，支持我需要在不同空间中记录代码和项目的文档支持（wiki和嵌入/版本控制），易于配置的问题跟踪器，控制，可换肤的网络界面和有用的社区。

解决方案

可能我建议一个名为fossil的新版本控制。

这不是我的项目，它是由Ri​​chard Hipp博士写的，他是做过SQLite的人。整个存储库都是一个SQLite文件，因此它非常稳固。你有一个维基和一个内置的票务系统。你可以有许多用户具有不同的权利，所以你可以例如让你的用户发行票，但不能查看源代码。

更多信息可以在

中找到，一个href =http://www.fossil-scm.org/ =noreferrer> http://www.fossil-scm.org/ ，如果你仔细观察，你会发现整个网站实际上是化石。

化石给我留下了深刻印象的一件事是，它只是一个文件，就是这样。整个化石项目是相当小的，但考虑到作者是谁，这并不是一个惊喜。

由于您的存储库是一个sqlite文件，您只需将其复制并且您有备份。

I'm a lone developer at the moment; please share you experiences on what is a good VC setup for a lone developer.

My constraints are;

• I work on multiple machines and need to keep them synced up
• Sometimes I work offline

I'm currently using Subversion(just the client to a remote server), and that is working ok. I'm interested in Mercurial and git DVCS, but none of their use-cases make sense to my situation.

EDIT: I've migrated my active development to Fossil http://www.fossil-scm.org/ after trialing it with a client. I really like the features to autosync my repositories(reducing accidental forks), the documentation support(both wiki and embedded/versioned) that supports my need to document the code and the project in different spaces, the easy to configure issue tracker, nice access control, skinnable web interface and helpful community.

解决方案

Might I suggest a rather new version control called fossil.

This is not a me too project, it is written by Dr. Richard Hipp, same guy who did SQLite. The whole repository is a SQLite file, so it is very solid. You have a wiki and a ticket system built in. You can have many users with varying rights, so you can for example give your users right to issue tickets but not view source code.

This is pretty simple, straight forward and it works as a distributed system, meaning you can clone and checkout locally and remotely.

More info can be seen on http://www.fossil-scm.org/ and if you look closely you see that the whole site is actually fossil.

One thing that really impressed me with fossil is that it is just one file, thats it. The whole fossil program is rather small, but considering who the author is, that is not really a surprise.

And since your repository is a sqlite file, you simply copy it and you have a backup.

这篇关于单独开发者的最佳版本控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！