use make and version control system for every project?

[Jorge Godoy]

Carl Banks <imbosol at aerojockey.invalid> writes:

> Why is that important?  How often do you really need to know when a
> bug was fixed, for example?  (I'm serious.  I've never needed to know
> these things.  Do other people really use these features for personal
> projects?  And if they do, is it really that often?)

Maybe your client calls you and says that the program is not working
as it should and say that he doesn't know the number of his version
immediately, but he remembers it was installed one or two weeks
ago... You remember solving such a bug, but when? 

> It's not what I was talking about, either.  Of course, version control
> is needed if there's more than a few people working on something.

To me, 'few = 0', but to you it might be 'few = 1' or more... This
varies from group to group too. We had a team that worked synced and
that could have 5 developers working very fine just by themselves, but
another team required a version control system for just 2 of
them...

Revision control systems are not a substitute for project management
and meetings. 



-- 
Godoy.     <godoy at metalab.unc.edu>