In my office we use MKS Source Integrity which is great from the Change Management & Workflow perspective. We used to use a combination of CVS, VSS & RCS repositories prior to migrating.
At home and when no one is looking I personally use Mercurial. (my vote) I really like the idea of a distributed system rather than a centralized one. It took me a little while to grok why it's better. I'm sure that everyone who uses Git probably went through the same awakening period to get over the paradigm shift.
The bottom line there is that there still can be a centralized repository but by having distributed repositories feeding into it you can improve the quality of the code that ends up in it. If nothing else it solves the age old debate about if you should check in any time you want or only when your code is working. Only working code should go into the main repository - and feel free to keep all the crap you want in your local one.
Wait! This isn't a Parachute, this is a Backpack!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||