[darkfader]

Has anyone considered using CVS or Visual Sourcesafe to maintain different versions, branching and merging things together again?
It's also easier to track who get credits for what modifications etc.
Cons:
- someone must learn to use the system to be able to check-in modifications... but not just anyone may do this anyway since it needs to be verified that it's working.
- CVS is not multi-server... which maybe would be bad for mods
- many other issues...

any other ideas?

[Ghworg]

Well, I for one can't imagine how anyone manages this project without source control. The first thing I did when I decided to try and change some stuff was to add the source to my own cvs server. I now have several branches for different mods, including one for my own testing and it is so much easier to transfer code between them.

I was disapointed when I checked sourceforge and saw that their cvs wasn't being used for eMule, it should be looked at IMHO.

[General Smirnov]

I totally agree. At the moment all i have is a different folder under the VS.NET projects folder and then i just copy source files across from one another in windows explorer. Inefficient to say the least...:-(
Although i guess the development teams for the original client and the mods are totally different, so one big combined cvs repository would be quite hard to co-ordinate and manage...I am sure each development team would use some sort of version control each...

[VQB]

We have already had a thread on this in the Dev forum.

The eMule project does use CVS -- just not the CVS at SourceForge.

And the Mods are completely unrelated to the official client as far as code management.

-VQB