Bad idea to maintain 20 branches of the same source code manually
I am looking for resources to explain to someone why it is a BAD IDEA to maintain 20 different versions of the same source code manually. I don't think I have done a very good job.
I am talking about treating a web application as if it were 20 different applications...when in practice it is just one application. Remembering what you did for Client A, then pasting that change into Client B, Client C, Client D, etc. And the other way around...take changes for B, C, and D and reintegrating them into A at some point, assuming A even slightly resembles something that B, C and D could even integrate into anymore.
Thanks for any help you can give...
I am talking about treating a web application as if it were 20 different applications...when in practice it is just one application. Remembering what you did for Client A, then pasting that change into Client B, Client C, Client D, etc. And the other way around...take changes for B, C, and D and reintegrating them into A at some point, assuming A even slightly resembles something that B, C and D could even integrate into anymore.
Thanks for any help you can give...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
what source control are you using?
ASKER
Right now - none.
This shop flies by the seat of its pants.
I'd like to give Tortoise SVN a try....
This shop flies by the seat of its pants.
I'd like to give Tortoise SVN a try....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thx
ASKER
They are and it is. I am trying to change their thinking.