我如何说服我的团队放弃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屋！