Hello.
I'm totally new with Vault.
Help me please, is there any Vault comparsion with VSS available? What features are new comparing with VSS? I couldn't find any on the website. I saw "Tips for SourceSafe Users" but it is too small IMHO.
I've downloaded demo Vault server and looks like VSS.
Does Vallt support optimistic locking - like CVS or Subversion? I mean that developers could edit one file and after commit changes will be merged.
Thank you.
Comparing Vault with VSS
Moderator: SourceGear
Here is some information:
http://software.ericsink.com/SourceSafe_to_Vault.html
It's dated, but still valid I believe.
Yes, Vault supports "optimistic locking", aka "edit-merge-commit":
http://software.ericsink.com/scm/scm_checkins.html
Cheers.
http://software.ericsink.com/SourceSafe_to_Vault.html
It's dated, but still valid I believe.
Yes, Vault supports "optimistic locking", aka "edit-merge-commit":
http://software.ericsink.com/scm/scm_checkins.html
Cheers.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear
-
oleksa
ericsink thanks a lot for fast answer.
Could you explain me please what will be happened if developer A will use check-out/edit/check-in and developer B will use edit/merge/commit paradigm. As far as I understood each developer could choose its own s ettings? So B is editing file 1 and A is checking out this file, and makes some changes. B initiates commit in this time while file is checked out by A. Will commit fails? Or changes made by developer A will be merged on check-in? Is it safe - mix locking paradigm in one project?
I've read File merge chapter but havn't found an answer
Could you explain me please what will be happened if developer A will use check-out/edit/check-in and developer B will use edit/merge/commit paradigm. As far as I understood each developer could choose its own s ettings? So B is editing file 1 and A is checking out this file, and makes some changes. B initiates commit in this time while file is checked out by A. Will commit fails? Or changes made by developer A will be merged on check-in? Is it safe - mix locking paradigm in one project?
I've read File merge chapter but havn't found an answer
Most of the developers at my company use the VSS style, require checkout. I use the edit-merge-commit style, mostly, except that I keep my local files read-only until I start to edit them. I do that so I have some feedback before I accidentally change an "important" header file (lots of dependencies).
Those using the VSS style will often make their local files writable to work on them, resulting in renegade files.
The main difference between the two is that they have to do a "check-out" action before the files show up in the pending change set, where I don't. The ability to merge the repository changes to the local version is not affected by these settings.
Someone using VSS style would be denied when they try to check out a file before check in. I haven't run into this yet, but I would imagine that someone using e-m-c would have their commit rejected because of an exclusive checkout.
Those using the VSS style will often make their local files writable to work on them, resulting in renegade files.
The main difference between the two is that they have to do a "check-out" action before the files show up in the pending change set, where I don't. The ability to merge the repository changes to the local version is not affected by these settings.
Someone using VSS style would be denied when they try to check out a file before check in. I haven't run into this yet, but I would imagine that someone using e-m-c would have their commit rejected because of an exclusive checkout.