Adam Glauser skrev  den 24-04-2008 15:11:
Another alternative is to find a hosting provider. Aaron Bartell
mentioned a Subversion hosting service that he particularly liked in his 
Subversion article in IBM Systems Mag 
http://www.ibmsystemsmag.com/i5/february08/developer/19751p1.aspx?ht=bartell%20bartell%20bartell
or http://tinyurl.com/4jx6mt.
  
That may be an option depending on your needs.
My experience is that it is quite beneficial to have such a server 
in-house as network services tend to be down when you REALLY need 
them.    A version control system is ALL your backups of ALL your source 
so if the server is down nothing is available to you.  This may not be 
very nice if you need to go back to a specific source snapshot to 
support a customer and you cannot do so for a day or two.
Some are more reliable than others, e.g. Google which usually is up as 
opposed to SourceForge who previously have had a lot of problems.
My point is that your versioning control system is so important to your 
development - you basically marry and have kids - that great care should 
be taken to get it right the first time.
We use CVS and have for a very long time.  We have considered migrating 
but are holding back simply because CVS happen to be well supported and 
we can live with not being able to rename files (while keeping the 
history).     The history is so important since it tells you what has 
been done by whom when, and hopefully - if they wrote it down - why they 
did so.
Just my opinion on the matter :)
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.