我如何说服我的团队放弃 sourcesafe 并转向 SVN? [英] How do I convince my team to drop sourcesafe and move to SVN?

问题描述

我的开发团队在非常基础的层面上使用安全源.我们正在进入一些更高级和更长的开发周期，我不禁想到，不使用分支和合并来管理更改很快就会让我们感到厌烦.

My development team uses source safe at a very basic level. We're moving into some more advanced and extended development cycles and I can't help but think that not using branching and merging in order to manage changes is going to be biting us very soon.

对于说服您的团队转向更好的解决方案(如 SVN)，您认为哪些论点最有用?

What arguments did you find most useful in order to convince your team to move to a better solution like SVN?

您使用哪些程序来弥补功能差距，以便团队不会错过 ide sourcesafe 集成?

What programs did you use to bridge the functionality gap so that the team wouldn't miss the ide sourcesafe integration?

或者我应该只接受 sourcesafe 并尝试将更好的做法硬塞进去?

Or should I just accept sourcesafe and attempt to shoehorn better practices into it?

推荐答案

首先，教他们如何有效地使用 SourceSafe.

First, teach them how to use SourceSafe in an efficient way.

如果他们足够聪明，他们会开始喜欢使用版本控制系统的优势，如果是这样，他们很快就会达到 SourceSafe 的极限.这就是他们将更能够听取您关于切换到更好的 VCS 的论点的地方，它是 CVCS 还是 DVCS，具体取决于团队准备实现的目标.

If they are smart enough, they will begin to love the advantages of using a version-control system, and if so, they will soon reach the limits of SourceSafe. That's where they will be the more able to listen to your arguments for switching to a better VCS, could it be a CVCS or a DVCS, depending on what's the team is ready to achieve.

如果你试图强迫他们在他们以错误的方式使用 SourceSafe 时使用另一个 VCS，比如保存源代码的 zip 文件(别笑，他们两年前在我公司就是这样做的)，他们会完全不愿意任何争论，尽可能好.

If you try to force them to use another VCS when they use SourceSafe in a wrong way, like saving zip file of source code (don't laugh, that's how they were acting in my company two years ago), they will be completly reluctant to any argumentation, as good as it could be.

这篇关于我如何说服我的团队放弃 sourcesafe 并转向 SVN?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！