> This is just a matter of discipline. Developer should always know what
> he/she is doing.
We're talkin' about Windows developers here. Har har.
In any case, if I were trying to leverage svn into an environment and my
engineers asked about integration with Visual Studio, saying 'You won't
want it. I promise. You don't know what you're doing.' isn't a good
enough (non-)answer.
That being said, the normal SCC integration is garbage, but some people
are accustomed to garbage. (People still use emacs, right?) I still
contend that ankhsvn (http://ankhsvn.tigris.org/) is as good or better
than any other SCC integration with Visual Studio, and when trying to
take a tool away and replace it with a new one, sometimes it's little
c*** like this that will start an uprising against the change. Getting
them to swallow a new methodology for code management will be hard
enough, piling on top of that lack of the interfaces they are used to
will make it even worse. Before the switch, it doesn't matter what's
really better or worse, the perception is that you're throwing a monkey
wrench at their daily routine.
It's a good idea to have as many legitimate answers to questions and
concerns from the developers and this package, when measured against
what already exists, stands up very well.
-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 05:39:45 2005