Distributed Developmentĭistributed development is at the heart of Git. However, rather than consider them all here, we’ll focus instead on what we like about Git and the benefits it offers over Subversion. We determined that Git is simply the more mature project. Mercurial (abbreviated, wisely, as “Hg”) offers a similar feature set and approach the two are really quite close to each other. Git is not the only choice for distributed version control, by any means. After careful consideration of the offerings out there (carried out primarily by our CTO, Jon Jensen), we determined that distributed systems were the best choice, and that Git is the winner in that category. It became clear that, for all of Subversion’s improvements over CVS, it was not the choice for the future. ![]() Of particular interest is the emergence of distributed version control systems, which offer a fundamentally different approach to change management than do the popular Subversion and its venerable predecessor, CVS.Ĭhoice is a wonderful thing, yet it brings a near-inevitable wringing of hands in its wake: how does an engineering team/company/guru choose between so many options? How can you be sure of choosing the right one? Perhaps you only recently moved from CVS to Subversion does the prospect of moving again provoke groans, and force consideration of the choice between what is good and what is easy?Īt End Point, we only relatively recently began using Subversion when, for a variety of reasons, we looked into the choices more deeply. The free software ecosystem abounds with good choices for version control software. The title is appropriate for the subject of version control with Git, as distributed version control as envisioned through Git represents a paradigm shift that must be embraced and understood in a fundamental way in order to shine. The article title “Better Git it in Your Soul” refers to the raucous, foot-stomping first track on the classic album Mingus Ah Um by Charles Mingus.
0 Comments
Leave a Reply. |