Version Control Systems (yes again)
-
Recently, my fascination is towards Distributed Version control systems and amazingly enough I saw this blog post on Martin Folwler's website. Is it a mere coincidence that so many people are talking about VCS or since I am interested in VCS, I am finding more peopl talk about VCS. Either way, here is the link to article: http://martinfowler.com/bliki/tools.html[^][^] and this http://martinfowler.com/bliki/VersionControlTools.html[^] Of course, it is not a scientiffic survey but I am not at all surprised by the results however. Except for Perforce and Baazar, I have used all the version control systems mentioned in the survey sometime or another: Subversion, git, Mercurial, ClearCase, TFS, CVS, Bazaar, Perforce and VSS. I never had any major issues with VSS especially in small teams. The only problems where due to IDE integration and branching. At my last place of work the development team migrated to Clearcase from a properietary VCS (built using batch files) and I found Clearcase to be worse than the batch files. TFS is great as a package but the source control part is nothing fantastic. I was not swayed either way by subversion. But the moment I saw Git and Mercurial I was immediately fascinated. I had some reservations about large code base and DVCS but when I saw that Linux repository was about 1 GB on Git, I no longer held my reservations. I wonder if people here have similar conclusions about VCS.
-
Recently, my fascination is towards Distributed Version control systems and amazingly enough I saw this blog post on Martin Folwler's website. Is it a mere coincidence that so many people are talking about VCS or since I am interested in VCS, I am finding more peopl talk about VCS. Either way, here is the link to article: http://martinfowler.com/bliki/tools.html[^][^] and this http://martinfowler.com/bliki/VersionControlTools.html[^] Of course, it is not a scientiffic survey but I am not at all surprised by the results however. Except for Perforce and Baazar, I have used all the version control systems mentioned in the survey sometime or another: Subversion, git, Mercurial, ClearCase, TFS, CVS, Bazaar, Perforce and VSS. I never had any major issues with VSS especially in small teams. The only problems where due to IDE integration and branching. At my last place of work the development team migrated to Clearcase from a properietary VCS (built using batch files) and I found Clearcase to be worse than the batch files. TFS is great as a package but the source control part is nothing fantastic. I was not swayed either way by subversion. But the moment I saw Git and Mercurial I was immediately fascinated. I had some reservations about large code base and DVCS but when I saw that Linux repository was about 1 GB on Git, I no longer held my reservations. I wonder if people here have similar conclusions about VCS.
First two years: No source control (me => scary) Next two years: VSS (me => oh this is cool) Next year: TFS (me => oh this is better, I don't think there's something better than this) This year: Git and Mercurial (me => holly crap, I've been with my head under the sand for so long, this is way better than any of those MS version controls). Between Git and Mercurial we opted by using Mercurial due to its VS integration and better tooling in general (I'm talking about a Windows oriented environment). But I've some pet projects where I use one or the other in order to master them (only time will tell ;) ).
-
First two years: No source control (me => scary) Next two years: VSS (me => oh this is cool) Next year: TFS (me => oh this is better, I don't think there's something better than this) This year: Git and Mercurial (me => holly crap, I've been with my head under the sand for so long, this is way better than any of those MS version controls). Between Git and Mercurial we opted by using Mercurial due to its VS integration and better tooling in general (I'm talking about a Windows oriented environment). But I've some pet projects where I use one or the other in order to master them (only time will tell ;) ).
emiaj wrote:
Git and Mercurial we opted by using Mercurial due to its VS integration and better tooling in general
Same, here. I want to standardize on one of either Git or Mercurial and I chose mercurial. One additional reason to better windows support was that codeplex and google code support it.
-
Recently, my fascination is towards Distributed Version control systems and amazingly enough I saw this blog post on Martin Folwler's website. Is it a mere coincidence that so many people are talking about VCS or since I am interested in VCS, I am finding more peopl talk about VCS. Either way, here is the link to article: http://martinfowler.com/bliki/tools.html[^][^] and this http://martinfowler.com/bliki/VersionControlTools.html[^] Of course, it is not a scientiffic survey but I am not at all surprised by the results however. Except for Perforce and Baazar, I have used all the version control systems mentioned in the survey sometime or another: Subversion, git, Mercurial, ClearCase, TFS, CVS, Bazaar, Perforce and VSS. I never had any major issues with VSS especially in small teams. The only problems where due to IDE integration and branching. At my last place of work the development team migrated to Clearcase from a properietary VCS (built using batch files) and I found Clearcase to be worse than the batch files. TFS is great as a package but the source control part is nothing fantastic. I was not swayed either way by subversion. But the moment I saw Git and Mercurial I was immediately fascinated. I had some reservations about large code base and DVCS but when I saw that Linux repository was about 1 GB on Git, I no longer held my reservations. I wonder if people here have similar conclusions about VCS.
Interesting. Thanks for the links. A while back I looked into Subversion, but it doesn't work the way I'm used to. I doubt the distributed systems do either.
-
Interesting. Thanks for the links. A while back I looked into Subversion, but it doesn't work the way I'm used to. I doubt the distributed systems do either.
PIEBALDconsult wrote:
it doesn't work the way I'm used to.
Distributed systems work very differently from traditional systems. It is very likely that the distributed systems will not work the way you are used to (if you are used to traditional check in and check out). But once you understand the flexibility offered by distributed systems you will never go back to a centralized system.
-
Recently, my fascination is towards Distributed Version control systems and amazingly enough I saw this blog post on Martin Folwler's website. Is it a mere coincidence that so many people are talking about VCS or since I am interested in VCS, I am finding more peopl talk about VCS. Either way, here is the link to article: http://martinfowler.com/bliki/tools.html[^][^] and this http://martinfowler.com/bliki/VersionControlTools.html[^] Of course, it is not a scientiffic survey but I am not at all surprised by the results however. Except for Perforce and Baazar, I have used all the version control systems mentioned in the survey sometime or another: Subversion, git, Mercurial, ClearCase, TFS, CVS, Bazaar, Perforce and VSS. I never had any major issues with VSS especially in small teams. The only problems where due to IDE integration and branching. At my last place of work the development team migrated to Clearcase from a properietary VCS (built using batch files) and I found Clearcase to be worse than the batch files. TFS is great as a package but the source control part is nothing fantastic. I was not swayed either way by subversion. But the moment I saw Git and Mercurial I was immediately fascinated. I had some reservations about large code base and DVCS but when I saw that Linux repository was about 1 GB on Git, I no longer held my reservations. I wonder if people here have similar conclusions about VCS.
I have a hard time seeing any benefits for me with respect to distributed VCS. At work it would be a real hassle I think. There are two questions that makes me hesitant: 1) Who's responsible for the builds that ship - who has the source code? 2) How is the backup solved? For now, Subversion works very well for our team. Today we're three people working with the repository, four within two months.
-- Kein Mitleid Für Die Mehrheit
-
I have a hard time seeing any benefits for me with respect to distributed VCS. At work it would be a real hassle I think. There are two questions that makes me hesitant: 1) Who's responsible for the builds that ship - who has the source code? 2) How is the backup solved? For now, Subversion works very well for our team. Today we're three people working with the repository, four within two months.
-- Kein Mitleid Für Die Mehrheit
Jörgen Sigvardsson wrote:
- Who's responsible for the builds that ship - who has the source code?
You can still have a central repository (just like the official linux/android distribution). The central repository will be where the users (you can even enforce restrictions as to who can push) will push their changes. All reviewed and merged code will go to that repository. Typically, this will be on the build machine.
Jörgen Sigvardsson wrote:
- How is the backup solved?
Backup the central repository or backup each users public repository, there are lot of options. It is very easy to convert a distributed system to a centralized system (in functionality) but reverse is not true. The wonderful thing to me is the flexibility with the distributed systems and it solves one big problem of incomplete checkins.
-
I have a hard time seeing any benefits for me with respect to distributed VCS. At work it would be a real hassle I think. There are two questions that makes me hesitant: 1) Who's responsible for the builds that ship - who has the source code? 2) How is the backup solved? For now, Subversion works very well for our team. Today we're three people working with the repository, four within two months.
-- Kein Mitleid Für Die Mehrheit
Jörgen Sigvardsson wrote:
- Who's responsible for the builds that ship
CHAOS method: Who ever does the last change the day it ships. (dude, you forgot to update before you built!)
Jörgen Sigvardsson wrote:
who has the source code?
CLK likes to occasionally suggest pruning the tree by intentionally deleting the repository and starting fresh. There are days I feel he is better trained as a gardener than I am, and that is saying something, because I put myself through VoTech gardening!
Jörgen Sigvardsson wrote:
- How is the backup solved?
backup? you mean the twin linux systems which require manual restarts, and are in two different buildings such that only the local one is ever restarted after major power outages and everyone forgot about the mirror system until it grew legs and walked away?
_________________________ John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others." Shhhhh.... I am not really here. I am a figment of your imagination.... I am still in my cave so this must be an illusion....
-
Jörgen Sigvardsson wrote:
- Who's responsible for the builds that ship
CHAOS method: Who ever does the last change the day it ships. (dude, you forgot to update before you built!)
Jörgen Sigvardsson wrote:
who has the source code?
CLK likes to occasionally suggest pruning the tree by intentionally deleting the repository and starting fresh. There are days I feel he is better trained as a gardener than I am, and that is saying something, because I put myself through VoTech gardening!
Jörgen Sigvardsson wrote:
- How is the backup solved?
backup? you mean the twin linux systems which require manual restarts, and are in two different buildings such that only the local one is ever restarted after major power outages and everyone forgot about the mirror system until it grew legs and walked away?
_________________________ John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others." Shhhhh.... I am not really here. I am a figment of your imagination.... I am still in my cave so this must be an illusion....
-
I've been pretty busy, plus lost most of my internet access during the day.
_________________________ John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others." Shhhhh.... I am not really here. I am a figment of your imagination.... I am still in my cave so this must be an illusion....