On 1/2/2014 5:25 PM, Mike Fochtman wrote:
Currently the team hasn't used any form of version control on these
applications because 'it would be too hard...'
I think you can get 99% of the way there by making sure that application
'A' is under full version control. Some version control is bette
> I'm part of a small development team (currently 4). We have two
> applications used in-house that consist of about 1900 source files. The two
> applications share about 1880 of the files in common, and there are only
> about 20 different between them.
>
> For a lot of complicated reasons I won'
If you can separate out the twenty files that might be different between
the two projects - put them into a different folder for the "A"
application as well, and not just for "B" - then your process likely
gets even easier.
Then you can have the files in "B" be a straight up ongoing branch of
I'm part of a small development team (currently 4). We have two
applications used in-house that consist of about 1900 source files. The
two applications share about 1880 of the files in common, and there are
only about 20 different between them.
For a lot of complicated reasons I won't go int
