On 10/30/15, Scott Doctor <[email protected]> wrote: > > That is my experience with all VCS systems. Even with fossil, I > am having trouble justifying why the hassle is worth the effort. >
What do you do when a customer calls to ask about code you sent them 18 months ago? How do you figure out what version of the code they are running? When you find an obscure bug that you know was not in the release from December 2012 but might have been introduced anytime between then and now, how do you figure out when it was introduced? How do you add experimental features and make experimental changes? Do you just start hacking away and hope the changes don't break anything? How do you identify versions of your code to your customer? How do you verify that no stray changes have been introduced into your code? How do you backup your code? When you have multiple people collaborating on the same project, how do you coordinate their changes and ensure that features added by one developer don't get overwritten and erased by another developers. How do you know who is working on what? Can you even identify what you code is? Seriously. I don't understand how it is possible to make reliable software without good version control. Is the foundation of everything. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
