version control / code consistency

[JimC]

Since to my count there are now 3 different people working on map-related code, how exactly are we going to maintain compatibility, and who is going to be in charge of this.

When coding gets more intense, this highly distributed coding effort is going to be a nightmare to manage.

I know it's dirty work, but somebody is going to have to take it on.

I haven't done any coding for about 2 weeks now (exams) but I'll post copies of my map-related code to whoever wants it, and they can criticise etc. and hopefully try not to deviate too much from what's already been done.

I'll be coding again by the end of the month.

Jim

[Mark_Everson]

Yep, I was hoping one of the professional programming types could point out the best way to do it... So over the next week or so we need to figure something out. I don't have any firm suggestions other than a simple check-out check-in system with a description of any changes that are likely to be made while the class is checked out. That's about the limit of my understanding of such things.

-Mark

[Druid2]

You need to define how the map data will be stored internally, and what the characteristics of the terrain or other conditions will be. Ideally this would be done prior to the start of coding, else you *are* going to have non-compatible program modules.

Ever hear the expression that managing programmers is like trying to herd cats?

[Rong]

A good model is the Mozilla project. The tool they are using is CVS (Concurrent Versions System).

BTW, I am still hoping this project can turn into an Open Source project. There is a nice paper about this development model called The Cathedral and the Bazaar.

If you decide to join the future , you can take a look at JOS, maybe even use their web site and CVS server.

Ok, that's enough URI's for one message.

------------------
The radical invents the views. When he has worn them out the conservative adopts them.
- Mark Twain

[This message has been edited by Rong (edited May 26, 1999).]