Quoting Thomas Harold <email@example.com>:
> CÚlio Cidral Junior wrote:
>> Here in my company we are trying to switch from VSS to Subversion, but
>> some programmers are a bit reluctant about it. It's well known and
>> already proved that VSS is weird, limited, buggy and problematic. One
>> of the questions was about what big companies are really using
>> Subversion in their development environment. Does anyone knows where
>> can I find a list of some of those big companies?
>> They also claim that all they need is just do check-ins and
>> check-outs, and don't want to get "complications". I think this
>> attitude may constraint the development process with rigid and
>> problematic procedures. What's your opinion about preventing the
>> development process from using goodies like branching, tagging and
>> also the copy-modify-merge model?
we changed 6 moths ago and have never looked back. even people who were
used to using checkin/outs via Visual Studio have come to love/like SVN
- transition was pretty smooth and it took relatively short time for
people ti get used toi the new model (few of them knew CVS already).
we are now looking forward to either team system or the new VSS. of
what i have seen and heard and read up untill now, neither of these
support *ANY* (useful) feature (source control wise) that we don't
already have in subversion.
> About the only thing that isn't in SVN yet is sharing, which we use
> extensively in VSS/SOS. That's supposed to get added at some point,
> but I'm also thinking about ways of doing without. (Sharing is very
> useful for managing things like websites where you might have a
> skeleton file that is identical across multiple folders, with changes
> managed in individual include files that aren't shared.)
eh, can you please explain exactly what VSS sharing can do that the
svn:externals property can not do more elegantly?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 23 09:46:26 2005