Source Control with Branching and VS support?
-
I've also heared about this new Shelving feature, and I see it's really something I would regulary use. But where is the difference between - Putting something "on shelve" - Putting it in an new branch. Is it just the benefit, nobody else sees my shelve ? Or minor adminstativ overhead?
From my understanding there really isn't any difference. TortoiseSVN does this naturally (unless you switch after branch) Subversion (by default) doesn't enforce any constraints on your repository structure, you find a convention that works for you. I like that flexibility. Of course you can use path-based authorisation or pre-commit hooks and to enforce rules if you really need them - we just use groups for authentication/authorisation, a pre-commit hook for enforcing log comments and a post-commit hook on some paths for email notifications.
-
Can anyone suggest a good write-up/tutorial on SVN with VS? Cheers Terry
Yes, the TortoiseSVN manual!
-
I work at a 150+ devcount site; we use VSTS/TFS2008, a necessity given the volume of projects and developers. But ... we are also running into ceiling issues with branching/merging and need MS consultancy to repair. TFS is by far the most mature source control system, but is actually not mature enough yet for flagship enterprise usage. Undoubtedly will become so in Rosario++. If you use VSS now and are in a 10+ developer situation, I still would advise migrating to TFS. You will however need someone (+ backup) with more than just suferficial knowledge of the workings of merging and branching. Tips and tricks are required, e.g. when it comes to issues due to renames, deletions, moves, simultaneously in changesets, branching for overlapping release management, component version integration issues, etc. etc.
Regards, Arjan Keene
"TFS is by far the most mature source control system" You're joking right? Not that maturity is any indication of quality *cough* VSS, but SVN is twice the age of TFS, Perforce, Mercurial, etc are all more mature VCS. "You will however need someone (+ backup) with more than just suferficial knowledge of the workings of merging and branching. Tips and tricks are required, e.g. when it comes to issues due to renames, deletions, moves, simultaneously in changesets, branching for overlapping release management, component version integration issues, etc. etc." Ah yes, I see that you are Joking :laugh:
-
Here is a question that I could use some help with. What is better CVS or Subversion in terms of featuresa and ease of use. Is there a easy to use client for subversion such as WinCVS is for CVS Thanks, Vaibhav
Subversion was written as a replacement for CVS, and designed to address its short-fallings, hence subversion kind of supersedes CVS. As to a replacement for WinCVS, well I've not used it so I couldn't say, but there are plenty of good SVN tools out there. By far the most popular is TortoiseSVN which integrates with Windows Explorer, or if you want a standalone client try checking out Subcommander or SmartSVN http://tortoisesvn.tigris.org/[^] http://subcommander.tigris.org/[^] http://www.syntevo.com/smartsvn/[^]
side lane digital development
-
A number of our developers were using PVCS. Now they've been pushed to use ClearCase. Most of them liked PVCS better -- although I think it's mostly that they were very used to it.
I second this comment about PVCS that was previously posted on codeproject PVCS even worse. Subversion is what I would recommend, just make sure you read the section on branching and merging in the docs before setting up your directory structure.
-
I've also heared about this new Shelving feature, and I see it's really something I would regulary use. But where is the difference between - Putting something "on shelve" - Putting it in an new branch. Is it just the benefit, nobody else sees my shelve ? Or minor adminstativ overhead?
ghard68 wrote:
Is it just the benefit, nobody else sees my shelve ? Or minor adminstativ overhead?
Its both.
The best way to accelerate a Macintosh is at 9.8m/sec-sec - Marcus Dolengo