We are currently using SourceSafe (multi user/version control program)and there is some dissatisfaction. I would like to know if anyone have pros or cons for other such software.
This will be cross posted at 8052 and SILabs fora
Erik
This is, I know, not a Keil question, but the results are used with Keil
I take the liberty to copy my 8052 post to this forum too.
Subversion or CVS are nice.
CVS are well-spread and is really concurrent. You normally don't lock the files but allow multiple persons to edit the same file. 19 times out of 20, CVS will correctly patch together changes from multiple users. When it sees that the changes collides, it will create a temporary file with your original data, and then patch the work file to contain both alternatives and let you manually solve.
The only disadvantage with CVS is that it doesn't version-handle meta-data. That makes it harder to rename files or move them between directories.
Supversion is basically a "next-generation" CVS and adds version handling of meta-data too.
Both the above choices have a good set of tools (command-line or graphical) for both Unix and Win32 users and quite a lot of programmers editors ir IDE allows integration.
One of the bad things with SourceSafe is that it compresses the file data. Todays harddisks are so large that you don't gain much by that. But a binary file means that if the source code repository gets broken, you may continue for days or weaks without knowing that you can't restore older versions. And when your backup has overrrun, you can't manually extract data from the binary file.
By the way: For CVS, I recomment the CVSNT version. It exists both for Win32 and for Unix and extends the traditional CVS a bit. It can also be bought in a commercial edition with support and optional real-time distribution of the repository between different sites.
And my reply is here:
www.8052.com/.../read.phtml
And my spelling of Subversion for some reason manages to mix between Subversion and Supversion...
Subversion + TortoiseSVN. Great tool.
I agree. Subversion fits small-scale in-house software development usage patterns perfectly. It might fit other usage patterns well too, but I don't have the experience. Large-scale open source projects might use other tools (Mercurial, Git), but that's a different story. It must be mentioned that there is the TortoiseCVS client for CVS which offers similar convenience. But the creators of Subversion claim that Subversion is a better CVS, and, based on my experience, I have to agree with them.
Large-scale probably has to be splitted into a number of sub-aspects: - many developers - geographically separated users - amount of trust placed on the individual developers
CVS and Subversion can handle huge projects, but a second issue is if how much you trust all involved developers and how much/hard you want to be able to control individual code updates. The requirements of a company with all developers located at the same office is very much different from the requirements in a distributed open-source project where some developers may be hostile, some may be stupid, and some may just be very bright but completely unsynchronized regarding the target goals.
We are currently using SourceSafe (multi user/version control program)and there is some dissatisfaction.
That must be the understatement of the month. The widely accepted point-of-view appears to be that using VSS is at best marginally less silly than printing the source code on paper and eating it. In other words: anything would be better than VSS. Even a pile of print-outs, as long as it's stored and indexed correctly.
Open-source has CVS (with some drawbacks regarding configuration management and massive multi-user use cases), and SVN (just about perfect). Commercial offers I've used and liked include Perforce (terrific for really large code bases) and MKS Source Integrity (includes well-done configuration tracking).
I once had to restore a system from a set of printouts - after the backups failed!
That was back in the days when taking a complete set of listings - on a lineprinter - and binding them all into a bigt folder was normal practice.
Don't knock it - it worked!
I once developed an optical backup system with ECC-korrected laser-printed bitmaps and read back with a scanner. I think I got about 75kB/page.
It was a fun thing to implement, and an alternative to 360, 1200 or 1440 kB floppies :)
The important thing with paper prints is that they can stand quite high temperatures, where a lot of magnetical material gets destroyed.
Hi All,
SourceAnywhere Standalone is also a good one. It is an SQL-based version control application that provides all of the key features of VSS, plus much more. SourceAnywhere Standalone comes with GUI client, command client, SDK, Eclipse plug-in, Visual Studio 6/2003/2005/2008 integration, Dreamweaver/Flash integration, cross-platform client. All are in one product. Besides that, SourceAnywhere Standalone offers a unique feature, Web Deployment through FTP.
Here is the home page of SourceAnywhere Standalone: www.dynamsoft.com/.../SourceAnywhere-SourceSafe-VSS.aspx
The SaaS Edition - SourceAnywhere Hosted is also available. www.dynamsoft.com/.../SourceAnywhere-Hosting-Version-Control-Source-Control.aspx
You can take a look.
Thanks.
Catherine Sea http://www.dynamsoft.com